App Won't Load - Android

[ertjlane]

Describe the bug Timeline: Lamp was successfully downloaded, user account logged in. Activity data was entered. Following morning app would not load, but continually buffered. Issue continued after phone was restarted, and after app was reinstalled. Unclear if phone logged out of account prior to issue arising.

To Reproduce Steps to reproduce the behavior:

1. reproducibility unclear. Occurred after app installation and sign on whenever app was opened. Reproduced on phone when opening mindlamp 2 app.

Expected behavior Expected to open lamp to activities screen.

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [motorola moto g(7) power]
• OS: [e.g. iOS8.1]
• Browser [chrome, irrelevant]
• Version [10]

Additional context NA

[ZCOEngineer]

We are checking this, shall update our findings/questions soon

[saranya-sajeev]

@ertjlane could you please share the log file?

[saranya-sajeev]

@ertjlane is this production or staging user?

[divyav2020]

We have logged in the app with the provided credentials. So far we have not experienced any issues. We are trying to reproduce the issue. We shall update here as soon as we find anything.

[avaidyam]

@divyav2020 Please also ensure you are testing on the closest possible Android device to the one @ertjlane is using.

[ZCOEngineer]

We were not able to reproduce this issue @avaidyam

[ZCOEngineer]

@ertjlane, @avaidyam is there a reccurence of this issue?

[avaidyam]

@ZCOEngineer As I haven't heard from @ertjlane that the issue persists, I'm going to close the issue for now.

[ertjlane]

The issue has occurred again, this time without the 403 error, but with an endless spinning wheel. The app has been uninstalled and reinstalled several times, and the phone restarted. The error has also occurred on another android device, specs listed below. Both devices have access to service and/or wifi.

On both devices mindLAMP had been previously installed, and a user had been logged in. On both devices the app was uninstalled, and then reinstalled. When the app was reinstalled, mindLAMP requested permissions as standard (phone calls, photos, motion, location, and recording audio). The app entered into the endlessly spinning circle as shown in the screenshot displayed above.

The user is, to my knowledge, irrelevant, since my user account would have been logged out upon uninstalling the app.

Device: U202AA OS: Android (version 9) Version [Hardware: V1.0, Software: v02.72.11]

Device: [motorola moto g(7) power] OS: [e.g. iOS8.1] Browser [chrome, irrelevant] Version [10]

[ZCOEngineer]

Hi @ertjlane, previously we were not getting this issue here, could you give us the user and credentials to check this here. it will be easy to debug the issue if we have an user who is currently experiencing this issue.

[saranya-sajeev]

@ertjlane Could you please share the log file if possible?

[avaidyam]

It seems like the Device: U202AA is actually an Android Go edition device? That could be a restrictive factor causing the issue.

[saranya-sajeev]

There is no emulator available with Android Go. Android Go devices having very limited memory. So we have tried to create an emulator with low memory and tried to install Lamp from play store, but the play store app exit after sometime and I have installed directly from Android studio. App showing spinner and then exits. App may not work properly on low memory devices.

[avaidyam]

@saranya-sajeev Thanks for the testing!

@ertjlane Can you update the documentation to share that we do not support Android Go or low memory/CPU devices?

[ertjlane]

@avaidyam @saranya-sajeev Yes I can do that. Thanks for looking into it guys!

[ertjlane]

This issue has occurred again. The user downloaded the app, but immediately upon opening it the endless blue buffering wheel appeared. The user quit the app, uninstalled and reinstalled it, and restarted their phone. The issue persisted. The user had not logged into the app. As seen below, this is not on a low memory device.

Samsung Galaxy S7 Android 8

[ZCOEngineer]

@ertjlane we shall check this

[divyav2020]

We have tested Beta and Production build in Samsung Galaxy S7 (Version 8). But we are unable to reproduce this issue. We will check in detail. Meanwhile could you please share the log

[ertjlane]

Thank you for looking into this. It will not be feasible to retrieve a log, as the user is a patient who likely cannot retrieve a log, and it wouldn't be appropriate to ask.

[avaidyam]

@divyav2020 We cannot provide log files from patients' devices. The most we can do is provide (via email only) the Participant IDs.

[michaelmenon]

@ertjlane is the patient trying to open the app in the hospital network or on his/her home network. Also can we ask the user to open this link the phone browser and see if its loading ?

https://dashboard.lamp.digital/

[ertjlane]

I've passed this on to the team managing the user, and they have directed the user to do as such. However, the team doesn't have very frequent contact with the user, and can't guarantee that they'll do this. I have directed the team to try doing the same on a similar device to see if there is a network problem. I would explore other avenues of evaluating the issue in the meantime, as we still may not be able to verify the problem through this route.

[ertjlane]

@michaelmenon This issue has occurred again, in a motorola e32, android version 11 (both phone and software quite recent). While I have asked the collaborator who brought this issue forward to provide more detail, I strongly suspect this is a non-user related issue, and is not the product of them operating a low memory device, and rather is an issue with the code. It has occurred with multiple android devices across the past several months, as documented here. Could the team please look into this, while I bring back any insight provided from the collaborators?

[ZCOEngineer]

@ertjlane sure we shall check this on our side as well, in the details you are requesting, could you ask for a video as well, and if possible get to know the steps they followed?

[ertjlane]

@ZCOEngineer Yes of course, I'll try to get as much detail as I can. Thank you for the prompt reply.

[michaelmenon]

@ertjlane we are looking into it and will let you know after our analysis. Meanwhile please send us any details you could gather. We suspect this issue with API taking time to load the data. We will confirm after our analysis.

[ZCOEngineer]

We are working on a retry mechanism. If the lamp web modules are not loaded in the expected time it will show a retry option. It also shows a retry option if the loading fails which was not handled earlier. App is given for internal QA and we shall update to staging beta once complete.

[ertjlane]

Sounds good, thank you!

[sijitg]

We pushed code and staging build is in review

[ertjlane]

This appears to be fixed in staging.