-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to switch Arcus platforms in app #1
Comments
This exists but is hidden - on the login screen, do a quick pinch three times from the outside in with two fingers and you'll get a selector to do this |
Hm, I logged out of the Arcus app and tried to do a quick pinch three times on various parts of the login screen, but nothing showed up. It'd be really useful if this was possible on the Iris app that's in the app store, but unfortunately it tries to make networking requests before the login page shows up (I believe it's testing whatever credentials are stored), and crashes when it can't connect. The latest version in the appstore just shows a shut down message and I wasn't able to get the menu to show up their either. |
Search for BuildConfigure.clientBundleVersion. That will help you solve the pinch issue |
Remove the check for if the bundle identifier matches the dev bundle identifier. Should fix the issue of not being able to bring up the DebugMenu |
Ok, I finally got around to following the advice provided (thanks again @Jamonek!). The current debug menu doesn't appear to allow a custom URL to be input, but does allow toggling between dev/prod. In order to get this in the app store, I think I'd need to add a prompt to select the Arcus Server (e.g. URL) on startup. This way the AppStore testing program can login to a pre-prod instance to verify functionality, and then end-users can pick the Arcus Platform they want to use. |
Ideally the app should support the ability to switch base URLs for the API, so that multiple Arcus platforms can exist, rather than requiring each platform to build a separate app.
The text was updated successfully, but these errors were encountered: