- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update target SDK version to 29 #106
Comments
Ready for AT on AT instructions:
|
App (branch) crashes with the following errors (on Android 10; seems to work on android 8) - and
|
It seems to be different. Looking into it. |
This comment says their issue was resolved by fixing a misconfiguration of the network on the phone which makes @ngaruko Can you provide details on how you tested this? Was it emulated or on an actual device? I assume you built and deployed it locally via USB? We need to replicate this on another device to test if it's specific to your phone... |
@njogz How did you get on with this? Is it possible to fix the bug without dropping crosswalk for Android 10? |
@garethbowen I haven't been able to find a solution that does not involve dropping crosswalk. I looked into required permissions introduced by android 10 as we had discussed but didn't have much luck with that either. |
All logs ( |
Pushing this back to In Progress as there is still investigation going on. |
I am not able to publish to the app store because of the target SDK version to 29. The app crashes. Has this been sorted out? |
@makombe it's in progress to be fixed right now. @garethbowen is doing the development on it. |
@newtewt Thanks for the feedback, eagerly waiting for the fix. |
Ready for AT in This branch adds a new android "flavour" for Android 10 and above which uses webview instead of crosswalk. Test that all the old supported features work, in particular: camera, GPS, mRDT, back button, etc. Also check performance against the old version to ensure that it's approximately the same. In addition this branch also includes a migration to copy data (pouchdb and cookies) from the crosswalk dir to the webview dir. It does not copy the service worker cache so you will need to have a connection when you first load the app to download the static files again. To test the migration...
It is hoped to roll the webview version out to Android versions 5 and above at a later date at which point we may need to put more work into making the migration smooth and user friendly, but we are in a hurry to get this step out in order to meet Play Store requirements so we can keep publishing the app. |
Testing on 2- upgradding from
Also expected since we are loading the app from different source and it is not going to be a production process - but wondering if we could give the
|
Re the |
Then |
Hi @garethbowen and @njogz cc @derickl and @billwambua |
@antonykhaemba |
That code isn't crosswalk, it's the crosswalk migration which runs every time the app starts. After the migration has run it fails to find files to migrate and does nothing. The log output is perhaps unnecessary but it shows it's working as expected. |
@garethbowen that script is used to retain the data when going from crosswalk to the newer webview version right? @ngaruko did you confirm that upgrading doesn't wipe the data? I thought side loading or installing from the gradle wipes everything so I'm a little concerned at how we would test that. |
Yes the script moves cookies (session) and indexeddb (pouchdb) data from the crosswalk dir to the webview dir. I tested during development by side loading from gradle and after reloading the app a couple of times I was automatically logged in and skipped the initial replication step. This proved to me that both cookies and indexeddb were being migrated correctly (albeit with some delay). This would not have worked if the gradle install wiped everything and I'm not sure why that would be happening for you. I'll try and get travis to push an alpha of the unbranded apk to the play store ASAP to make testing easier and more production-like. |
@garethbowen I think we need a way to handle connection errors presented by chrome. I have to close the app to get rid of the error and then ensure I am connected to data. I am able to get the connection error message by
|
We used to detect that and render a error message with a "retry" button. I'll investigate what changed and try and reimplement it. |
@newtewt I've fixed a regression where we added a slightly nicer error message and a retry button at the bottom of the error page. I think this is broken in the Crosswalk version too so I'm not sure when this regression occurred. I'm still working on getting the alpha build to be published, so to test you can either wait for that, or build the apk from source. |
@antonykhaemba We're putting the final touches on testing now - so far so good. Have you got an exact date you need this release by? Would you be interested in a pre-release apk so you can do some testing of your own? |
The Safari Doctors project is supposed to go live on 1st of December 2020. Yes I would be interested in testing the pre-release apk? @garethbowen cc @billwambua |
@antonykhaemba Great. I expect to have a release out some time this week and will let you know as soon as it lands. If you want to have a go before that you can create your flavour branch from the |
I've finished all my testing that I can and put my results on the spreadsheet. I guess my only concern is with @garethbowen's comment (below) means we can't fully test the play store upgrade on Android 10 😞
However, @garethbowen has a LOT more experience than me with this, so I'll defer to him!! |
This bumps the target SDK version for Play Store compliance. It also introduces a webview based flavor for Android 10+ devices with a data migration step. The build has been modified so it doesn't publish each brand's app. It also adds a "gamma" brand for internal testing. #106
This has been released in v0.6.0 |
This bumps the target SDK version for Play Store compliance. It also introduces a webview based flavor for Android 10+ devices with a data migration step. The build has been modified so it doesn't publish each brand's app. It also adds a "gamma" brand for internal testing. #106
There are upcoming deadlines regarding target SDK version for updating or publishing new apps.
The text was updated successfully, but these errors were encountered: