Skip to content
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

fix(android)(8_0_X): Refactored activity/fragment restore handling #10868

Merged
merged 9 commits into from Apr 26, 2019

Conversation

- [TIMOB-26966] Fixed bug where back navigating from child window causes app to exit when "Don't keep activities" is enabled as of 7.2.1.
- [TIMOB-26914] Fixed 8.0.0 regression where an OS forced quit app displays a blank window upon relaunch. (Was incorrectly restoring child activity.)
- [TIMOB-17089] Resolved view ID conflicts causes app crashes when activity/fragment is restored.
- [TIMOB-26964] Fixed bug where TabGroup would be blank (no tabs) when calling child window's close() method while "Don't keep activities" is enabled.
- [TIMOB-26890] Fixed bug where tapping 3rd tab in TabGroup can cause a crash due to view ID conflict during fragment restore.
- Increased TabGroup's ViewPager offscreen page limit from 1 to 128 to avoid tab fragment from being destroyed/restored.
- Added several safety mechanisms to AlertDialog and ProgressIndicator dialog code to avoid crashes.
…hin a fragment such as "ti.map" view

- Re-added ID assigned to TiUIFragment's view, but it's now guaranteed to be assigned a unique ID.
…f "Don't keep activities" is enabled as of 8.0.0
- [TIMOB-15829] Fixed crash caused by progress indicator set to status bar that happens after hiding twice and then opening.
- [TIMOB-26966] Fixed bug where Window/TabGroup close()method call is ignored until "open" event has been fired.
  * Resolved by modifying proxy's handleClose() to call TiActivityWindows.remove() immediately.
- Fixed bug where dynamically changing "exitOnClose" would be ignored.
  * Flag was only being read by activity's "launchIntent" in 8.0.0.
  * Now reads directly from proxy, which is the best solution. Especially if onNewIntent() was called. (Old code would have had a problem too.)
- Re-added support for "exitOnClose" in child windows. (Was only supported by root window.)
- Removed window exit animation if its "exitOnClose" was set true. (Prevents parent window briefly appearing upon exit.)
- Added more dialog safe-guards.
  * Would crash if failed to create dialog builder if there are no activities available.
  * Can happen if "Don't keep activities" is enabled, you press the Home button, and code attempts to show dialog in the background.
@build
Copy link
Contributor

build commented Apr 26, 2019

Messages
📖

💾 Here's the generated SDK zipfile.

📖

✅ All tests are passing
Nice one! All 3025 tests are passing.

Generated by 🚫 dangerJS against ad17272

@lokeshchdhry
Copy link
Contributor

FR Passed.

The activity/fragment refactor looks good.

Studio Ver: 5.1.2.201903111843
SDK Ver: 8.0.1 local build
OS Ver: 10.14
Xcode Ver: Xcode 10.1
Appc NPM: 4.2.13
Appc CLI: 7.0.10
Daemon Ver: 1.1.3
Ti CLI Ver: 5.1.1
Alloy Ver: 1.13.9
Node Ver: 8.15.1
NPM Ver: 6.4.1
Java Ver: 10.0.2
Devices: ⇨ google Nexus 5 (Android 6.0.1)
⇨ google Pixel (Android 9)

@lokeshchdhry lokeshchdhry merged commit 584d038 into tidev:8_0_X Apr 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants