Difference between revisions of "Android troubleshooting"
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
'''Answer''' | '''Answer''' | ||
| − | :You may have used one of our Beta versions. Please stop the regify application and uninstall completely. Upon successfully uninstall, you can install the app from the Android App-Market again. | + | :You may have used one of our Beta versions. Please stop the regify application and uninstall completely (using Taskmanager or Settings -> Applications -> Manage Applications). Upon successfully uninstall, you can install the app from the Android App-Market again. |
Revision as of 17:36, 13 December 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).
- Additionally, Android needs a regify Provider with at least V3.0.1 to work.
- If you are a provider: 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. We also think, that, depending on the Android Version, there may be a problem with wildcard certificates. Please use a named certificate (for the complete domain) for your regify-provider.
Problem
- Android is complaining about an invalid signature while installing.
Answer
- You may have used one of our Beta versions. Please stop the regify application and uninstall completely (using Taskmanager or Settings -> Applications -> Manage Applications). Upon successfully uninstall, you can install the app from the Android App-Market again.
