Uncaught Exception Error

[Devayani0102]

Describe the bug User U7851221787 on android device LG K30 experienced random 'Uncaught Exception' error. Restarting the app removes the error.

Additional context Similar error in issue #645

Screenshots

Smartphone (please complete the following information):

• Device: LG K30

[saranya-sajeev]

@Devayani0102 We have already fixed this issue and is available in beta build. Could please check the beta build?

[saranya-sajeev]

@Devayani0102 We will test here and update you.

[divyav2020]

We have checked this issue in latest Beta build and we couldn't reproduce it.

[ZCOEngineer]

We shall check more in detail and update

[michaelmenon]

This seems to be fixed in beta. it should get resolved once we push beta to production.

[ZCOEngineer]

This issue appears same as #645 , as that was handled and pushed to beta please test this on current beta android version.

[ZCOEngineer]

We got this exception once last day. we have updated the library for google fit and given for testing. shall update beta if we does not get this exception.

[avaidyam]

@ZCOEngineer Please mark the issue in progress or QA testing if this is the case. Thanks!

[saranya-sajeev]

@avaidyam Invalid end time issue not got reproduced after library update so we have pushed the code to beta and is in review status.

[Devayani0102]

The User U7851221787 on the android device LG K30 is still experiencing the invalid end-time issue. Below is the StackOverflow for the error:

java.lang.IllegalStateException: Invalid end time: 1657383131860
at com.google.android.gms.common.internal.Preconditions.checkState(com.google.android.gms:play-services-basement@@18.0.0:3)
at com.google.android.gms.fitness.request.DataReadRequest$Builder.build(com.google.android.gms:play-services-fitness@@20.0.0:155)
at digital.lamp.mindlamp.sensor.GoogleFit.queryFitnessData(GoogleFit.kt:574)
at digital.lamp.mindlamp.sensor.GoogleFit.<init>(GoogleFit.kt:70)
at digital.lamp.mindlamp.repository.LampForegroundService$collectSensorData$timer$1.onTick(LampForegroundService.kt:298)
at android.os.CountDownTimer$1.handleMessage(CountDownTimer.java:130)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:205)
at android.app.ActivityThread.main(ActivityThread.java:6993)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:884)

[avaidyam]

@Devayani0102 If you feel the participant is willing to test the staging build then they may do so and provide feedback, but otherwise you will need to wait for this fix to reach production status before the issue is resolved for the participant.

The GitHub issue will be closed as the issue is resolved in staging and can be reopened if you or others test staging and still encounter the issue.

[ertjlane]

We've recently had two users experience this same issue. For one the issue would arise spontaneously, and does not pop up specifically when opening mindLAMP but opens spontaneously.

Samsung Galaxy S21 and Samsung Galaxy S8+ (android version 9).

[saranya-sajeev]

are they using production or beta build?

[ertjlane]

Production!

[divyav2020]

Could you please check this in beta build? Currently this change is not updated in production

We are also trying to reproduce this issue in current beta build in above mentioned devices

[avaidyam]

@divyav2020 This should have been released to production already. @saranya-sajeev @michaelmenon Can you check on/confirm what happened to the build?

[ZCOEngineer]

@avaidyam we had informed @carlan1 to move android to production from beta (https://github.com/BIDMCDigitalPsychiatry/LAMP-platform/issues/692#issuecomment-1251893603)

Currently when release is created production pointed build is pushed to beta. We believe last time you moved it to production.

[michaelmenon]

Hi @avaidyam , I think once we move to beta your team tests the beta and then move that to production. I will confirm with @carlan1 in our call this week to move this to production.

[michaelmenon]

@ertjlane we will check on the 705 in beta and see if this is the same exception. and confirm. #648 which is this thread is updated in beta and needs to be pushed to production and I think your team used to push to production.

[avaidyam]

@michaelmenon Thanks for the clarification, we’ll make sure to do that ASAP.

[carlan1]

Android release has been made and is in review.