[TIMOB-17232] iOS: Analytics - Killing an app before the session timeout is generating a new session
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | None |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2014-06-28T01:43:10.000+0000 |
| Affected Version/s | Release 3.3.0 |
| Fix Version/s | Release 3.3.0, Release 3.4.0 |
| Components | iOS |
| Labels | module_analytics, qe-3.3.0, qe-testadded |
| Reporter | Wilson Luu |
| Assignee | Sabil Rahim |
| Created | 2014-06-27T17:38:19.000+0000 |
| Updated | 2014-07-09T17:38:30.000+0000 |
Description
*Details:* Killing an app before the session timeout is generating a new session i.e. ti.background and a new ti.foreground (new sid) is sent.
*Note:* This does *not* occur on native Android i.e. killing the app (backing out) and relaunching before a session timeout does not generate a new session.
*Steps to reproduce:*
1. Create a default app in Xcode with APS analytics enabled OR import check.zip into Xcode
2. Install app onto device and wait for app to launch; point device to staging
3. Next, background the app, wait a couple of seconds, then kill the app (double-press home button and swipe up on app)
4. Bring the app back to the foreground before 30 seconds
*Actual:* ti.background and a new ti.foreground is sent (see payloads.txt attachment).
*Expected:* ti.background and ti.foreground should not be generated.
https://github.com/appcelerator/titanium_mobile/pull/5873 https://github.com/appcelerator/titanium_mobile/pull/5872
Verified fixed on: Mac OSX 10.9.4 Appcelerator Studio, build: 3.3.0.201407081443 Titanium SDK, build: 3.3.0.v20140708132513 Titanium CLI, build: 3.3.0-rc4 Alloy: 1.4.0-rc4 iOS Device: iPad Air (7.1.2) Followed steps in the description. If application is backgrounded and foregrounded again before the session timeout, and since we are still in the same session, no analytic payloads are sent for the background and foreground. Any new payloads sent after this background and foreground will have the same session ID. Closing.