[TIMOB-6763] iOS: App Crashes trying to play sound while app resumes from background.
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | Critical |
|---|
| Status | Closed |
|---|
| Resolution | Fixed |
|---|
| Resolution Date | 2012-02-14T23:29:04.000+0000 |
|---|
| Affected Version/s | Release 1.8.0.1 |
|---|
| Fix Version/s | Sprint 2012-03, Release 2.0.0, Release 1.8.2 |
|---|
| Components | iOS |
|---|
| Labels | n/a |
|---|
| Reporter | Mauro Parra-Miranda |
|---|
| Assignee | Vishal Duggal |
|---|
| Created | 2011-12-19T14:57:26.000+0000 |
|---|
| Updated | 2012-02-14T23:29:04.000+0000 |
|---|
Description
Problem description
Customer compiled his app with the new Mobile SDK 1.8RC3 and it's getting continuous crashing (at startup, when sending audio, etc.).
STEPS TO REPRODUCE
1. Install app into device
2. Start another instance of the app in the simulator
3. Follow the setup instructions in the section "EXTRA INFO"
4. Send audio and photos from the device to the simulator app.
4. Close the app in the device.
5. Send several messages from the app in the simulator, to the app/number in the device.
6. Resume the app in the device
EXPECTED RESULTS
The app able to receive the data.
ACTUAL RESULTS
The app is crashing.
EXTRA INFO
You can get the source code from the dropbox:
CE Team Share (shared with Steven Tramer and Marshall). Others can be added to access this source as necessary.
flobby-gt2appcelerator-d69a09e50fff07296c384da08ff1b8cf3f51dd5a.zip
Here is more setup info.
Testing: You will need to setup your iphone and the simulator. Once installed the app into the two devices, you will need to go to the agenda and add a number, doesn't matter which number you put, let's say you assign:
Device = +1-650-11
Simulator = +1-650-12
Then you wil need to add the simulator number to the Device's address book, and viceversa. When you start the app, you will need to "register" the device, add the device number to the device login, and the simulator number to the simulator.
Attachments
Is there a console log at all on this? This is caused by an exception.
I've been trying for over an hour, and still can't recreate the crash. I just saw the console log, but unfortunately, it doesn't help.
Aha. Okay, to get the proper log, I'll need you to go to XCode, press Command-shift-2. Then you'll see a window similar to this screenshot. Choose devices up top, the phone on the left side, console there, and copy-paste the text there into here.
*Still* no luck on getting this to recreate, even with CE trying here as well. In talking with Thomas, he suggested we get all the info to try to recreate this as best as possible. What we need: The version of TiStudio. The version of XCode installed. The version of Mac OS X on the mac. The device and iOS version number. The iOS version used in simulator. Then, if at all possible, it'd be great to get the actual built files from a build that's showing this behavior. That is, the actual build folder that contains the generated xcode project and application. This will be a hefty size, but it may hold the key as to what's going on.
When you get a build shipped in that shows this behavior, try and get a dSYM file to go with it so that we can symbolicate logs. If we've got the whole project + a build (with the xcodeproj) this won't be as big an issue since we can regenerate it, but still. Even an IPA file we can attach the debugger to might be enough, if it comes with a dSYM. We should probably start requesting these as well for full-app problems from customers as part of the report.
These crash logs indicate the debugger was being used. This is another bug that is fixed, TIMOB-6572.
Possibly resolved by TIMOB-6572.
asking Shaks group to close