April 13, 2023
Risk assessment and release recommendation
Dev, PM, and QA teams have completed QA and signed off on 4/19/2023. There were no regression bugs found during testing and no test pass fails. The release risk is low and we recommend release to the App stores on cadence on 4/24/2023.
Build information:
Contact Sonia or Erin if you do not have access to the test app builds.
Platform | Build | Access |
---|---|---|
Android PROD | 31 (0.25.31) | QR code |
Android Test | 34 (0.27.34) | https://play.google.com/apps/internaltest/4699629181922915622 |
Android | Full Changelog | Comparing v0.25.31...v0.27.34 · Sage-Bionetworks/MobileToolboxApp-Android (github.com) |
Northwestern Android |
|
|
iOS PROD | 1.4.1 (97) | QR Code |
iOS Test | 1.4.3 (102) | Testflight App |
iOS | Full Changelog | Comparing v1.4.1...v1.4.3 · MobileToolbox/MobileToolboxApp-iOS (github.com) |
Northwestern iOS | no build included in this release | NA |
Researcher portal PROD |
| |
Researcher portal TEST |
| https://staging.studies.mobiletoolbox.org/
|
This mobile client release addresses
PSM (Arranging Pictures) restarts on some small screen iOS devices if the border was accidentally swiped. The previous fix was a workaround to get PSM to function with the implementation of background recorders. Apple recently released an update, and now the fix can be better implemented.
The previous update to schedule caching has been improved so that the adherence record is fetched every time on launch. This addresses a scenario where a participant may have a long session window open and receive an app update, switching devices, or an uninstall. The adherence record was not previously fetched on the update, so the schedule was being re-served to some participants. This issue caused duplicate exposure to assessments and most heavily impacts the UCSF study where a long session window of 6wks increases chances that a participant would update the app during a session. This fix covers the scenario if they update that they receive the right schedule where they left off instead of repeating assessments.
Text on the Account Profile tab to instruct a participant how to withdraw from a study had an error and was presenting as ‘to_withdraw_account’. The full text has been restored.
Turn on capability to show a screen to instruct a participant that they need to update the app before continuing IF we receive a 410 Not Supported error code. This is to ensure that critical updates are taken by participants before they proceed and to ‘unstick’ them from a broken state.
Show data upload status on the Today screen
Additional crashlytics logging was added to monitor, capture, and diagnose previous and new issues.
Improvements to handling 410 re-auth failures that were occurring with background uploads
TBD – Android notes from Northwestern (but will likely include PSM crash fix)
This data pipeline release addresses
No change to ETL pipeline. Two bugs were fixed to address retroactive data that was stuck at data processing. This was a fix to a broken array crawler and a fix to the bootstrap trigger to start processing. These bug fixes do not impact data format or content, only infrastructural fixes
No change to scoring pipeline
work currently in progress to recompute DCCS. An issue was discovered at the point of data collection from the mobile device, so current recomputation plan needs to be re-evaluated by the scientific owner before finalizing a change to computation.
work is currently in progress to operationalize the scoring code. One fix in code review is a fix to make the scoring pipeline robust to additive metadata changes. Ie, the pipeline should not fail as long as its input requirements are met, even if there are additional metadata fields available that it should ignore.
QA recommendations
Jira ticket | Title | Platform | Recommended test scenarios | QA team(s) |
---|---|---|---|---|
PSM restarts when swiping too close to edge on small screen devices | iOS | Swipe edge near notifications on small screen (iphone 12 mini, 2nd gen SE) during practice and during actual assessment. Use E2E QA study. | Sage, NU | |
Participant receives duplicate session on their schedule | iOS, Android | Install a build prior to May 2022 (build 18 for Android, build 1.2 for iOS). Open a session and complete activities. Leave app open. Take the update, switch devices, or uninstall. Open schedule and verify that duplicate schedule is not served. Use a non-persistent study. | Sage | |
| Update ‘to withdraw from study’ text | iOS | Open Account/Profile and validate that correct text appears no ‘to_withdraw_account’ | Sage |
Capability to show a screen to instruct a participant that they need to update the app before continuing IF we receive a 410 Not Supported error code | iOS, Android | This is not testable via UI alone, need a different app environment | Sage | |
| Show data upload status on the Today screen
| Android | Open app, check assessments are scheduled. Turn off wifi. Complete assessments. Reconnect to wifi, open today screen | Sage |