tabGroup.close() doesnt work on Android, please suggest alternate solution as my application is shutting down after showing black screen. However I am calling new Window to open as before tabGroup.close() is called, But Application is throwing exception as follow.
355)] jsValueToJavaObject returning null [ERROR]TiBaseActivity( 355) [8679,42904] Layout cleanup. [WARN][InputManagerService( 61)] Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@44f5a660 (uid=10040 pid=355)
From the docs:
On Android, only one tab group may exist at one time. A tab group may be closed to allow a new one to be opened later, but the root of the application must be a heavyweight window to prevent it exiting. Tabs cannot be removed from the tab group once added, and tabs cannot be reordered.
On iOS, more than one tab group may exist, and the may be opened and closed as required. Each tab can contain a stack of windows, and the user can switch between them by tapping the tab's associated control. Tabs can be removed, and the user may (optionally) be allowed to reorder tabs.
I think we're beyond the point where I can give you any help. You're trying to brute force a solution that will not work on android.
This won't help you much at this point, but maybe it will help others who are just getting started. If you want to build a cross-platform application, DO NOT fall into the trap of just testing on the iOS simulator, even though that's the fastest tool we have available. DO test at least once per day on all target platforms. Every time you try adding a new view to your application, test on all target platforms. Every time you try handling new events, test on all target platforms.
There are so many differences between the platforms that you need to catch any issues as they arise. Trying to deal with an entire app's worth of inconsistencies would be painful at best, impossible at worst. In this case, Umaid has built his app's entire structure around a concept that does not work on android, which will ultimately force him to do some heavy restructuring (or give up on android).
Believe me, it is possible to write an app that runs well on both iOS and android. But you have to commit to both platforms from the beginning of your project.
Think you can help? Login to answer this question!