Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-4941] Android: More graceful workaround for Android Bug 2373 & 5277

GitHub Issuen/a
TypeBug
PriorityHigh
StatusClosed
ResolutionFixed
Resolution Date2012-03-12T10:08:28.000+0000
Affected Version/sRelease 1.7.2
Fix Version/sRelease 2.0.0, Sprint 2012-06
ComponentsAndroid
Labelsmodule_package, qe-testadded
ReporterPedro Enrique
AssigneeNeeraj Gupta
Created2011-08-08T14:54:14.000+0000
Updated2019-01-11T03:28:50.000+0000

Description

Comments

  1. Mark Aalderink 2011-08-29

    I hope you will give this high priority. I've got a client that complains about this. And I've seen it mentioned in reviews of apps as a negative.
  2. Don Thorp 2011-10-08

    Pull Request: https://github.com/appcelerator/titanium_mobile/pull/541 Additional configuration options were added. The values shown below are the defaults. 
       <property name="ti.android.bug2373.disableDetection" type="bool">false</property>
   <property name="ti.android.bug2373.restartDelay" type="int">500</property>
   <property name="ti.android.bug2373.finishDelay" type="int">0</property>
   <property name="ti.android.bug2373.skipAlert" type="bool">false</property>
   
       <property name="ti.android.bug2373.message">An application restart is required</property>
   <property name="ti.android.bug2373.title">Restart Required</property>
   <property name="ti.android.bug2373.buttonText">Continue</property>
    if disableDetection is true, then the workaround is disabled and it will be possible for the app to be launched multiple times if opened first via install then opened from Home. restartDelay is the number of milliseconds to wait before launching the app again with the corrected Intent settings. finishDelay is the number of milliseconds to wait before telling the original Activity with the incorrect Intent settings to wait before finishing itself (i.e. exit) if skipAlert is true, then the AlertDialog will not be displayed and an Android Toast will be displayed with the contents of ti.android.bug2373.message. If the message is set to an empty string, then the Toast will not be displayed.
  3. Don Thorp 2011-10-08

    Testing Notes. See TIMOB-1559 for the general test instructions. The cases that should be tested are minimally. 1) No tiapp.xml settings. Should exhibit current TIMOB-1559 behavior. 2) disableDetection = true. Should exhibit 2373 and 5277 behavior, basically launch multiple times. 3) skipAlert = true. Should see Toast with message 4) Verify "Old Settings" modify dialog and background 5) Verify message change works when skipAlert = true 6) Try different restartDelay and finishDelay settings to prove they change 7) Verify empty message and skipAlert = true does not display a Toast Message.
  4. Thomas Huelbert 2011-12-10

    QE - update packaging test plan with these test steps
  5. Thomas Huelbert 2012-02-08

    closing and tagging for future port
  6. Shak Hossain 2012-03-12

    De-escalating it.
  7. Marshall Culpepper 2012-03-12

    We implement the suggested workarounds already, and have further recently fixed this for Kindle Fire and 3.x devices
  8. Wilson Luu 2012-03-15

    Closing bug. Verified fix on: SDK build: 2.0.0.v20120315070246 Runtime: v8, rhino Titanium Studio, build: 2.0.0.201203142055 Devices: Droid 1 (2.2.3), Xoom (3.2.1), Kindle Fire
  9. Paul Hamilton 2012-05-21

    This alert is now appearing whenever the app is fired from the market, regardless of whether it was launched from the homescreen first. Android 2.3.3
  10. Paul Hamilton 2012-05-21

    also, this is particularly hazardous when the user first installs the app. If they try to launch from the notification bar, a common thing to do. The first thing they see is that the application needs to be restarted. using SDK 2.0.1.GA2
  11. Paul Hamilton 2012-05-21

    also, this is particularly hazardous when the user first installs the app. If they try to launch from the notification bar, a common thing to do. The first thing they see is that the application needs to be restarted. using SDK 2.0.1.GA2
  12. Neeraj Gupta 2012-05-21

    @Paul - Please open a new ticket with the exact scenario. This ticket already has several different use cases.
  13. Paul Hamilton 2012-05-21

  14. grebulon 2014-08-20

    A similar thing happens when launching an app from the lock screen. You need to set the lock screen to slide mode, and put your app as one of the shortcuts. Now kill the app if it's running, lock the phone and slide to your app. Then lock again and slide again - a second instance will run. Now if you lock again and slide to your app, it will bring the second instance into focus.
  15. Joshua Quick 2019-01-11

    This issue has been resolved in Titanium 8.0.0. Please see: [TIMOB-26075]

JSON Source