Thank you Ismael,
My supervisor is aware of the http/https issue. Thank you for your help on troubleshooting this.
On a related note, when testing the app yesterday, I found that the mobile app did not like the `pulldata(“@json” . . . )` but it would allow me to use the `pulldata(“@geopoint” . . ). It is my understanding from some of the help online that once a locator url is identified it is referenced in the following geocoding calculations, but I found that not to be the case. I guess the question here is, should I use @geopoint for all geocoding calculations in the survey or can I reference a json created from first calculation?
Thanks,
Ian