Survey123 not working after update to Android 12

1046
5
02-02-2022 04:55 AM
GarrettBergey
New Contributor II

We have a survey that is launched via collector (or field maps). It was working fine until one of our devices updated from Android 11 to Android 12. When we go to launch the survey via collector we get an error message saying download survey123 (even though it is already downloaded). We made sure all apps were updated and tried deleting and reinstalling survey123 but we continue to get the same error. The survey is working normally on other devices that were not updated to Android 12. The device in question is a Samsung Galaxy S10 Lite. Any help would be greatly appreciated.

0 Kudos
5 Replies
JamesTedrick
Esri Esteemed Contributor

Hi @GarrettBergey ,

Just to check, are teh links you are using "arcgis-survey123://" or "https://survey123.arcgis.app"?

With Android 12, Google made a few changes to how app links work. We're researching the exact cause, but in the meantime you can long-pres on the app, select App Info, and then click teh 'Open by default' section to Add the https://survey123.arcgis.app domain as an approved link.

0 Kudos
JamesTedrick
Esri Esteemed Contributor

@GarrettBergey,

We've identified the issue in the app link configuration and have corrected it (it was a misconfiguration of the website that is associated with the app link).  The app link now works.

0 Kudos
GarrettBergey
New Contributor II

@JamesTedrick 

Thank you for your assistance on this. We are now able to use the survey. The only issue that we are still having is that instead of directly opening survey123 it first takes you to a web browser (see image below):

GarrettBergey_0-1643993738808.jpeg

If you click on the survey123 icon it will open the survey. Is there a way to skip this additional step? 

 

Thanks, 

 

Garrett

 

Tags (1)
0 Kudos
Strahanjen
Occasional Contributor II

Did you find a solution for getting the link to open Survey123 directly rather than going to the download page? I'm encountering the same issue. 

0 Kudos
GarrettBergey
New Contributor II
Our issue actually went away. I believe that one of the ESRI updates corrected the problem. Good luck with your issue!
0 Kudos