Difference between revisions of "Android troubleshooting"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | '''Problem | + | '''Problem''' |
:Android App is not able to get configuration from provider (even if provider >= V3.0.1). | :Android App is not able to get configuration from provider (even if provider >= V3.0.1). | ||
| − | '''Answer | + | '''Answer''' |
:In most cases the internet access is not given (does not work in browser, too). We've had the problem, that the used provider-certificate has not been recognized by the Android SDK (browser worked, regify APP does not). The problematic SSL certificate has been a RapidSSL certificate. After switching to Limitbreaker from http://www.psw.net or Thawte SSL123, the problem has been gone. | :In most cases the internet access is not given (does not work in browser, too). We've had the problem, that the used provider-certificate has not been recognized by the Android SDK (browser worked, regify APP does not). The problematic SSL certificate has been a RapidSSL certificate. After switching to Limitbreaker from http://www.psw.net or Thawte SSL123, the problem has been gone. | ||
Revision as of 08:34, 20 September 2011
Problem
- Android App is not able to get configuration from provider (even if provider >= V3.0.1).
Answer
- In most cases the internet access is not given (does not work in browser, too). We've had the problem, that the used provider-certificate has not been recognized by the Android SDK (browser worked, regify APP does not). The problematic SSL certificate has been a RapidSSL certificate. After switching to Limitbreaker from http://www.psw.net or Thawte SSL123, the problem has been gone.
