Uploaded image for project: 'Titanium SDK/CLI'
  1. Titanium SDK/CLI
  2. TIMOB-24427

Alloy app started from secondary activity fails horribly

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Environment:

      Android 5.x, 6.x.

    • Story Points:
      13
    • Sprint:
      2019 Sprint 1

      Description

      We have a need to utilize multiple activities within our titanium/alloy application. This is a very common paradigm for Android development. However, the basic example is not able to work properly. We have created a Stack Exchange issue (http://stackoverflow.com/questions/42376926/how-to-create-an-appcelerator-alloy-android-application-with-multiple-activities) as well as a github repo demonstrating the problem (https://github.com/DaKaZ/multiactive).

      It would be possible to work around the problem IF titanium would update `Ti.Android.currentActivity.intent` if the activity is re-launched with a new intent. That way we could the information on the extra keys in the current activity.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jquick Joshua Quick
                Reporter:
                dakazmier Michael Kazmier
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Backbone Issue Sync

                  • Titanium SDK/CLI <> Titanium Mobile
                    Synced with:
                    TIMOB-10506
                    Sync status:
                    ERROR
                    Last received:
                    Last sent:

                    Git Source Code