-
Notifications
You must be signed in to change notification settings - Fork 64
Default www
is hardcoded and required
#33
Comments
I tried fixing the So the issue remains: once the app is killed and restarted, we're back with the original version, not the update. It does not ask for another update then, so it's registered as properly installed, just not loaded up when the app is freshly started. I feel like this would be a super simple fix in the right place, but I wasn't able to find it. Again, forking this repo and trying to modify the |
We got to the point where Android Studio logs show
I feel like this is directly related to the issue you are discussing. Not being able to find the start page could be caused by hardcoded paths. FYI, I have |
Signed-off-by: Clovis Durand <[email protected]>
Signed-off-by: Clovis Durand <[email protected]>
Signed-off-by: Clovis Durand <[email protected]>
Signed-off-by: Clovis Durand <[email protected]>
…commands Signed-off-by: Clovis Durand <[email protected]>
…commands Signed-off-by: Clovis Durand <[email protected]>
…commands Signed-off-by: Clovis Durand <[email protected]>
Ok, so I fixed it by replacing the I'll submit a MR later today. |
…commands Signed-off-by: Clovis Durand <[email protected]>
Signed-off-by: Clovis Durand <[email protected]>
So, @Clovel can you confirm the updates actually stick after app restarts? I thought I had fixed it on iOS by renaming |
I confirmed it is working for Android. I'm currently battling with my Xcode installation to test this on my iPhone. I'll keep you posted. You can take look @ my MR if you want : #35. Feedback is appreciated. |
So, after testing on iOS, I get an exception when (or after ?) applying the update. Here are some of the logs I got before the exception. Logs
|
I strongly believe that this is caused by the The plugin should be compatible with no signing. The android side works like that. @mittermayr perhaps you could try my fixes with a private/public key. |
I fixed this (#33 (comment)) problem. MR coming soon. Thus, I can confirm that the CodePush updates do in fact stick. |
@Clovel thank you so much for pushing this lib forward! |
Just for anyone else who finds this who already worked around the issue with a bit of scripting... You can get appcenter to bundle things correctly by creating a temporary folder with 'www' as the "leaf node" containing the built app/index.html and assets. This folder will now need to be called 'public'.
Then point the appcenter-cli to this folder using |
Description
When building with Angular/Ionic/Capacitor for Android, the final assets output is located in
./android/app/src/main/assets/public
. The path used in the AppCenter CLIupdateContentsPath
flag, or-c
is apparently relevant to the checks performed internally (or maybe used to name the resulting zip file.) Therefore, executingappcenter codepush release -a "whatever" -c "./android/app/src/main/assets/public"
prevents the update files from being found. If you move the files to awww
folder (or renamepublic -> www
, it works.tl;dr
www
is hardcoded. If the resulting extracted dir is based on the zip filename, that should be used, or otherwise expose a config.The text was updated successfully, but these errors were encountered: