Hi, We're attempting to run a workflow in Geocortex mobile while the app is in the background or the device is locked. Has anyone had any luck attempting this?
The workflow runs when we have the app open and if you leave the app or lock the device then return to the Geocortex mobile app the workflow continues to run, but for the time that you were away from the app it does not run. So far we have only tested on IOS but will be testing on Android shortly (will update here with results). The IOS device has background app refresh turned on and location is enabled always.
Thanks in advance
-
UPDATE: Have tested with Android; same behaviour as IOS
0 -
Hi Chris,
Thanks for your feedback. We have noted issues in previous releases with idling the app during testing; I've added your notes the issue when we revisit this behaviour in future releases.
Stefan
0 -
Thanks Stefan. Out of interest is Geocortex mobile being able to run a workflow in the background a capability that is currently supported, or is it expected behaviour that it doesn't work? Would you expect this to work if decided to build the app and deploy it to an app store?
0 -
Hi Chris,
There are many factors that impact how the app will respond when backgrounded, with workflow being one of the more complex. We are aware of the outstanding issues, which will require additional work to fully support in a seamless manner.
Mobile supports running a workflow while actively using the app, but locking the device or switching between apps while a workflow is running will be looked at as a future improvement.
Thanks, Stefan
0 -
Thanks @Stefan Schweigert? that's helpful. We are going to go down the build-app route on Android and see how that goes. I will reply here with the result.
0 -
UPDATE:
We have attempted using the build-app process to build an Android app. However when I attempt to deploy the app to the google play console it fails with the error; "You need to reduce your APK file size to 100MB or use APK expansion files." The app has one very small workflow in it and little to no other functionality and the APK file is 131MB. Is it expected that APK from running the build-app process should result in a file that is too large to be deployed without splitting the app using expansion files? Is there a recommended process to create the expansion files without impacting the functionality of the app?
Happy to create this as a new question if preferred.
0 -
Hi Christopher,
We are planning on providing a maintenance release to address this issue in the coming weeks. This releases includes a change to the build service which allows users to generate a .AAB file, which is the new format you will need in the future for Android Play Store submissions, and generates an artifact which is small enough to be submitted.
Thanks, Stefan
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
7 Kommentare