You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If geteduroam is the preferred option to install CAT profiles, please provide a debug log option so that us NROs who find that our members are rolling it out and are having issues can at least diagnose what might be going wrong, and provide advice.
I really would appreciate that option, it will help you as well given it should be able to give you a more accurate picture of the devices being used (and possibly what errors may occur on different patch levels of the OSes).
Seriously, implement something. Even it it's just the ability to get the end state and save the information that led to the error, i.e. whatever is needed for the call, plus OS information, patch level etc, and the ability to paste it into an email or a text note on the device. On iOS, add something in settings to control the option, on Android, put a hamburger or gear menu in somewhere that allows you to set an option to capture the information? Anything that gives you better information about the problem is better than a tapping around in the dark based on some vague information a student might've given you (or the support desk at a university that now comes to you with the problem). It can help make the app better.
The text was updated successfully, but these errors were encountered:
The easiest place to flag profiles that will not be entirely compatible is, I'm afraid, CAT itself. There should be debugging in adb, I think that's the common approach to debug Android Apps? See also the Slack conversation. I don't think we can add debugging from inside the App, at least not under A11.
If geteduroam is the preferred option to install CAT profiles, please provide a debug log option so that us NROs who find that our members are rolling it out and are having issues can at least diagnose what might be going wrong, and provide advice.
I really would appreciate that option, it will help you as well given it should be able to give you a more accurate picture of the devices being used (and possibly what errors may occur on different patch levels of the OSes).
Seriously, implement something. Even it it's just the ability to get the end state and save the information that led to the error, i.e. whatever is needed for the call, plus OS information, patch level etc, and the ability to paste it into an email or a text note on the device. On iOS, add something in settings to control the option, on Android, put a hamburger or gear menu in somewhere that allows you to set an option to capture the information? Anything that gives you better information about the problem is better than a tapping around in the dark based on some vague information a student might've given you (or the support desk at a university that now comes to you with the problem). It can help make the app better.
The text was updated successfully, but these errors were encountered: