[TIMOB-4160] iOS: KitchenSink no longer presents notification when it goes to background
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Invalid |
Resolution Date | 2011-05-20T19:22:39.000+0000 |
Affected Version/s | Release 1.7.0 |
Fix Version/s | n/a |
Components | iOS |
Labels | kitchensink, tbs-1.7.1 |
Reporter | Eric Merriman |
Assignee | Blain Hamon |
Created | 2011-05-20T12:03:46.000+0000 |
Updated | 2017-03-09T23:00:14.000+0000 |
Description
Description:
KS does not throw an alert when it goes to the background. Console output from KS being placed in background to launching again is:
Fri May 20 11:56:32 unknown UIKitApplication:com.appcelerator.pushtest[0x10c3][68700] : [INFO] app was paused from the foreground
Fri May 20 11:56:32 unknown KitchenSink[68700] : [Warning] Deregistering for sleep notifications when we have not registered
Fri May 20 11:56:32 unknown com.apple.launchd[1] : (com.apple.mobile.installd.mount_helper) posix_spawn("/usr/libexec/installd_mount_helper", ...): No such file or directory
Fri May 20 11:56:32 unknown com.apple.launchd[1] : (com.apple.mobile.installd.mount_helper) Exited with exit code: 1
Fri May 20 11:56:32 unknown com.apple.launchd[1] : (com.apple.mobile.installd.mount_helper) Throttling respawn: Will start in 10 seconds
Fri May 20 11:56:38 unknown UIKitApplication:com.appcelerator.pushtest[0x10c3][68700] : [INFO] app is resuming from the background
Fri May 20 11:56:38 unknown sandboxd[68817] : KitchenSink(68700) deny iokit-open RootDomainUserClient
Fri May 20 11:56:38 unknown KitchenSink[68700] : [Warning] IORegisterForSystemPower failed
Fri May 20 11:56:38 unknown UIKitApplication:com.appcelerator.pushtest[0x10c3][68700] : [INFO] app has resumed from the background
Fri May 20 11:56:38 unknown KitchenSink[68700] : [Warning] IMLocalObject died: [IMLocalObject] Port Name: com.appcelerator.pushtest-listener
Steps to reproduce:
1) Install and launch KS
2) Click the "home" button to background KS
Result:
No alert is presented
Expected Result:
Alert with "close" or "Resume" and very excited text describing the fact that KS is now in the background
Notes:
This may be considered intermittent as I have just witnessed the alert for the first time this pass. I'll try to provide more data around frequency.
Turns out it's as designed: On the first launch, the notification happens, but the JS specifically asks to stop the background service once it's done. Tested this on 1.6.2 and had same behavior.
Closing ticket as invalid.