Difference between revisions of "Android troubleshooting"

From regify WIKI
Jump to navigation Jump to search
 
(8 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
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.
 
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.
  
===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===
 
In most cases the internet access is not given (does not work in browser, too).
 
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.
 
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.
  
 +
==Usage==
 +
===Opening regipay messages triggers error 61===
 +
If you get error 61 ("no decrypted regify file available") during opening of regipay messages, the PDF reader on your device may be defect or wrong installed. Please try to install an alternative like the free [https://play.google.com/store/apps/details?id=com.google.android.apps.pdfviewer Google PDF Viewer] and try it again.
  
==Usage==
 
 
===I can not open rgf files (regify messages). Android complains about no assigned application.===
 
===I can not open rgf files (regify messages). Android complains about no assigned application.===
We know about this problem on Samsung Galaxy devices. It turned out, that Samsung is using a customized e-mail app that differs from the standard Android e-mail app. In this customized version, all file extensions and mime-types are hard-coded and the client is only able to open messages with one of these extensions. Sadly, it is impossible for others to assign their extension to that. Thus, we can not assign the rgf extension.
+
We know about this problem on older Samsung Galaxy devices. It turned out, that Samsung is using a customized e-mail app that differs from the standard Android e-mail app. In this customized version, all file extensions and mime-types are hard-coded and the client is only able to open messages with one of these extensions. Sadly, it is impossible for others to assign their extension to that. Thus, we can not assign the rgf extension.
 
As a solution, you may use another (more standard compliant) e-mail application like [https://market.android.com/details?id=com.fsck.k9 K9 Mail].
 
As a solution, you may use another (more standard compliant) e-mail application like [https://market.android.com/details?id=com.fsck.k9 K9 Mail].
  
Line 30: Line 30:
 
Please check any firewall or security software that is able to control internet access of your apps. Maybe the regify app is blocked by this software?
 
Please check any firewall or security software that is able to control internet access of your apps. Maybe the regify app is blocked by this software?
  
We have information on some customers having problems with German '''Congstar''' plans. There is currently no solution for this. Try the same device with another SIM card to verify this problem.
+
We have information on some customers having problems with German '''Congstar''' plans. There is currently no solution for this. Try the same device with WLAN. If this also does not work, try another SIM card to verify this problem.
 +
 
 +
=== Open regify messages in the Gmail app ===
 +
Some versions of the Gmail app seem to only accept some default file extensions within e-mails and you can't open the rgf-file directly. After tapping this attachment, GMail usually displays it as a text file or as regify container file. Now you can tap on the share-button on the navigation bar (upper right corner) and you can select the regify app as the application to open the regify message. If you do this, the regify message will be opened by the regify app as usual.
 +
 
 +
Sadly, we can not fix this behaviour as it is done wrong by Google GMail app. The regify extension is properly assigned to the regify app, but GMail is ignoring it. As an alternative, please consider using another e-mail program from the Google Play Store.
  
 
==Debugging==
 
==Debugging==
  
===Start extended debug logging===
+
=== Version 2.0 and above (released end of 2024) ===
Beginning with version 2.1.0 of the regify-app for android, you can get a detaild debug-log. To activate debugging you have to enter the settings menu and tapping on the provider logo very quick for at least four times. After that, an additional field for enabeling the debugging will be appear. Here you have to add a check. For reading the logfiles you also need a tool like [https://play.google.com/store/apps/details?id=com.nolanlawson.logcat Catlog] on your device.
+
 
 +
You can enable and disable debug logging in the app settings menu. Please activate debugging and then replicate the issue you have. Now enter settings again and click the button to send it by email.
 +
 
 +
If your issue comes up before login (eg login issues), please tap the logo image 5 times until you get the debug options. This activates debugging and shows some additional functions. Now replicate the issue you have. Then, enter this screen again (or app settings if login was successful) and click the button to send the debug log by email.
 +
 
 +
If you have other issues and want to reset all configuration, please tap the logo image 5 times until you get the debug options. There you will find a button to wipe all settings. After it was clicked, close the app completely and restart it.
 +
 
 +
'''BETA:''' If you want to run the beta version channel, tap the logo image or the About screen headline minimum 10 times. The QA menu will pop up. There you can switch the channels (beta/release) and then reload the app.
 +
 
 +
=== Version 1.3 ===
 +
 
 +
To activate debugging you have to enter the iPhone settings menu. In this menu you will find an entry for the regify app. In the submenu of the regify app, you can activate the debug mode. After that, logging will be activated and a Send Log-file button will appear on login screen next time, in the fallback login screen and settings menu.
 +
 
 +
If your issue comes up before login (eg login issues), please tap the logo image multiple times until you get the debug options. There, activate debugging and then replicate the issue you have. Then, enter this again and click the button to send the debug log by email.

Latest revision as of 14:18, 9 August 2024

Installing

Android is complaining about an invalid signature while installing.

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.

Android App is not able to get configuration from provider

In most cases the internet access is not given (does not work in browser, too).

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.

Usage

Opening regipay messages triggers error 61

If you get error 61 ("no decrypted regify file available") during opening of regipay messages, the PDF reader on your device may be defect or wrong installed. Please try to install an alternative like the free Google PDF Viewer and try it again.

I can not open rgf files (regify messages). Android complains about no assigned application.

We know about this problem on older Samsung Galaxy devices. It turned out, that Samsung is using a customized e-mail app that differs from the standard Android e-mail app. In this customized version, all file extensions and mime-types are hard-coded and the client is only able to open messages with one of these extensions. Sadly, it is impossible for others to assign their extension to that. Thus, we can not assign the rgf extension. As a solution, you may use another (more standard compliant) e-mail application like K9 Mail.

I have many mails that state that I'm the wrong receiver (specially on K9 mail). On other receiving clients, the same messages open with no problem.

If K9 mail is configured to download not the complete mail, the rgf attachment may not be completely downloaded. You will find a button "download complete message" on bottom of your message. You need to click this button first before opening the regify message. You can also configure K9 in that way, that it downloads not only the first kilobytes in order to prevent such problems.

I received a file named Winmail.dat?

It seems, that the sender of this e-mail sent you the message using Outlook. You can find more information here: Wikipedia on TNEF In short, please ask the sender to switch the e-mail format from RTF to HTML or Text. We found out that Outlook uses always TNEF (Winmail.dat) in case you are sending to yourself (same recipient e-mail address than your sending one).

You also can give the sender a hint about the following internet ressources:
http://blogs.msdn.com/b/deva/archive/2007/12/19/tnef.aspx (wann OL und Exchange Winmails.dat senden)
http://support.microsoft.com/kb/138053
http://support.microsoft.com/kb/278061

I can not get it to run. It waits forever after entering e-mail address and password.

Please check any firewall or security software that is able to control internet access of your apps. Maybe the regify app is blocked by this software?

We have information on some customers having problems with German Congstar plans. There is currently no solution for this. Try the same device with WLAN. If this also does not work, try another SIM card to verify this problem.

Open regify messages in the Gmail app

Some versions of the Gmail app seem to only accept some default file extensions within e-mails and you can't open the rgf-file directly. After tapping this attachment, GMail usually displays it as a text file or as regify container file. Now you can tap on the share-button on the navigation bar (upper right corner) and you can select the regify app as the application to open the regify message. If you do this, the regify message will be opened by the regify app as usual.

Sadly, we can not fix this behaviour as it is done wrong by Google GMail app. The regify extension is properly assigned to the regify app, but GMail is ignoring it. As an alternative, please consider using another e-mail program from the Google Play Store.

Debugging

Version 2.0 and above (released end of 2024)

You can enable and disable debug logging in the app settings menu. Please activate debugging and then replicate the issue you have. Now enter settings again and click the button to send it by email.

If your issue comes up before login (eg login issues), please tap the logo image 5 times until you get the debug options. This activates debugging and shows some additional functions. Now replicate the issue you have. Then, enter this screen again (or app settings if login was successful) and click the button to send the debug log by email.

If you have other issues and want to reset all configuration, please tap the logo image 5 times until you get the debug options. There you will find a button to wipe all settings. After it was clicked, close the app completely and restart it.

BETA: If you want to run the beta version channel, tap the logo image or the About screen headline minimum 10 times. The QA menu will pop up. There you can switch the channels (beta/release) and then reload the app.

Version 1.3

To activate debugging you have to enter the iPhone settings menu. In this menu you will find an entry for the regify app. In the submenu of the regify app, you can activate the debug mode. After that, logging will be activated and a Send Log-file button will appear on login screen next time, in the fallback login screen and settings menu.

If your issue comes up before login (eg login issues), please tap the logo image multiple times until you get the debug options. There, activate debugging and then replicate the issue you have. Then, enter this again and click the button to send the debug log by email.