"End Trip + Sync" not working on iOS

[MelvynLi]

Hello,

We are testing out an installation of e-mission and so far it seems to be running fine, with only one issue. In our testing, some users report the diary screen "hanging" and not updating with the latest trips/new trips not showing in the "label" page after being immobile for a few days. We found out that on Android, the option "End trip + sync" in the "developer zone" section of the profile tab fixes this and uploads any trips that are in limbo, and causes trips to resume tracking correctly again.

However, on iOS it seems this function does not work and if it is selected, it shows the same notification "all trips pushed!" as Android, but the latest trips do not show up and it does not resume tracking trips until you log out and log back into the app. This is problematic as logging out and logging back in seems to discard any previous un-processed/un-uploaded trips even if the trip tracking resumes.

Have these issues been encountered before, both the trip tracking stopping after being immobile/not making any trips for a few days, or the "End trip + sync" not functioning on iOS?

Thank you!

[shankari]

@MelvynLi In general, it would be helpful to provide additional details that would help us get a better understand of what you are running.

Concretely:

• what are the server and phone versions? (e.g. what is your HEAD commit?)
• what does your configuration look like? which authentication method? which auxiliary scripts? OpenPATH is a complex system and has several moving parts.
• have you checked the logs on the phone and the server? Do you see any errors? Note

  e-mission-docs/docs/manage/troubleshooting_app_faq.md

  Line 65 in 29cc1e6

  In order to demonstrate this technique, I manually introduced an error in one of the files by commenting out the closing parantheses

For iOS, if you haven't pulled recently, the issue might be
e-mission/e-mission-server#1021 or
e-mission/e-mission-server#1008

I am not aware of upload issues on android, but am happy to take a look at the logs if you can send them over.

[MelvynLi]

• Our branch appears to be 25 commits behind e-mission/e-mission-phone:master, the server code was cloned around the same time around September 2024. Perhaps we can try merging our phone branch with the official e-mission one and updating the app to see if anything changes.

• I don't believe we have any auxiliary scripts running, is the authentication method defined in the following line in the study configuration?: "aggregate_call_auth": "user_only"

• I have attached the error logs from the server, I noticed the webserver error file does not contain any recent errors (only ones from November 2024 when we were setting up the server) however the intake_0 file does have more recent ones (latest Feb 12)

  intake_0-errors.log
  webserver-errors.log

• I do not have the logs from the user's phone at the moment, I will try to see if I can obtain them

Thank you!

[shankari]

There have been some fairly significant bugfixes to the phone code since then, particular e-mission/e-mission-phone#1189

We are also in the process of making additional scalability improvements to the analysis pipeline (e-mission/e-mission-server#1014 (merged) and e-mission/e-mission-server#1017 (ETA next week))

We strongly encourage you to run the https://github.com/e-mission/e-mission-server/blob/master/bin/push/silent_ios_push.py script (we do this every hour) so that any backlogged data is uploaded properly, at least on iOS.

OpenPATH is under active development, so I encourage you to pull frequently; your bug may already have been fixed!

I will take a look at your logs tomorrow!

[MelvynLi]

Thank you for the suggestions, we will try and merge the code since then and see if it resolves our issues, then report back.

[shankari]

@MelvynLi just checking in to see if this is now working.

Were you able to enable the silent push?
Are the entries then getting pushed to the server appropriately?