You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2018. It is now read-only.
I recently ran into a serious bug where my CI builded APK's where the hot code push plugin was not functioning. Even error events were not emitted. However, my own test builds worked just fine.
After close inspection, the only difference between my test builds and the CI builds, was this one line in the res/xml/config.xml file:
There is an empty chcp tag at the top of the config.xml file. There is a second chcp tag near the bottom that includes the proper config-file tag.
The only difference in my test setup and the CI setup, is that the CI builds the APK's from scratch every time. I could replicate this issue in my test setup by running these commands:
This prevents a timing issue where the initial prepare created an empty
chcp tag in config.xml that causes the plugin to stop functioning.
Fixesnordnet#70
I recently ran into a serious bug where my CI builded APK's where the hot code push plugin was not functioning. Even error events were not emitted. However, my own test builds worked just fine.
After close inspection, the only difference between my test builds and the CI builds, was this one line in the res/xml/config.xml file:
There is an empty chcp tag at the top of the config.xml file. There is a second chcp tag near the bottom that includes the proper config-file tag.
The only difference in my test setup and the CI setup, is that the CI builds the APK's from scratch every time. I could replicate this issue in my test setup by running these commands:
You will notice the empty chcp tag in the top. When preparing a second time, the empty chcp tag is removed. I suspect this is a timing issue.
I created a PR that removes the empty tag in the plugin.xml file. This resolves the issue.
The text was updated successfully, but these errors were encountered: