[TIMOB-25398] Android: Alert window does not appear with remote security policy when device is offline
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | None |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2019-02-05T01:17:05.000+0000 |
Affected Version/s | Release 6.1.0, Release 6.0.4, Release 6.2.2 |
Fix Version/s | Release 7.0.0 |
Components | Android |
Labels | Android, qe-6.2.2, regression |
Reporter | Abir Mukherjee |
Assignee | Joshua Quick |
Created | 2017-10-16T22:54:41.000+0000 |
Updated | 2019-02-05T01:17:05.000+0000 |
Description
*Description*
An app built with remote security policy is expected to pop up an alert when the device is offline. This used to work for SDK < 6.0.4. However, for SDK versions 6.0.4 - 6.2.2 (current GA), the alert does not pop up and stays on the splash screen. This is a regression.
*Steps to reproduce*
1. Create a default classic app.
2. Add this to tiapp.xml:
<property name="appc-sourcecode-encryption-policy" type="string">remote</property>
3. Set up the test device to have no network connectivity.
4. Build and launch the app to an Android device.
*Actual Results*
For the affected versions, the app stays at the launch screen, and the expected pop up alert does not pop up.
*Expected Results*
An alert should pop up.
*Note:*
Documentation for this feature can be found here...
https://docs.appcelerator.com/platform/latest/#!/guide/tiapp.xml_and_timodule.xml_Reference-section-src-29004921_tiapp.xmlandtimodule.xmlReference-appc-sourcecode-encryption-policy
appc-verify: https://github.com/appcelerator/appc-verify/pull/12 appc-cli-titanium: https://github.com/appcelerator/appc-cli-titanium/pull/248
Passed FR. [~fmiao] can you please merge?
[~amukherjee], pending
appc-cli-titanium
PR update.[~amukherjee] This is currently marked for 7.0.1 but seems merged, can we correct the milestone to 7.0.0?
[~hknoechel] I moved it back to 7.0.0. There were some required updates which didn't make it in time for beta, but apparently those changes have made it since then, so I corrected fixVersion back to 7.0.0.
Verified that fix is in RC 7.0.0 build.
Re-opening since this is still an issue... or perhaps the fix wasn't up-ported. I was able to reproduce it in 7.3.0, 6.3.0, 6.1.1, and 6.0.4. It works in 6.0.2.
This issue needs to be fixed on the CLI side. To be fixed by ticket: [CLI-1343]