iOS app crashes when closing with NSException
I had a working iOS app with Jukebox music library and background audio. However, an hour after everything was working well, the app started to crash with
libc++abi.dylib: terminating with uncaught exception of type NSException
every time I close the app. Usually the music used to continue playing in the background, but now the app crashes. I also opened an old project that was only working well, but the same error came up.
The app works well in the simulator, but not on the device.
I didn't post any code because I literally didn't change things in the old project at least for it not to work anymore and crash. What should I do? The outlets are good btw.
EDIT
Here's the stack trace:
What's weird is that I tried the app on my friend's iPhone 6 running 12.1 and it worked with no issue, however when I do it on my iPhone 6S running 12.1 it crashes. What do I do in this case?
swift crash ios-simulator device nsexception
asked Nov 13 '18 at 0:13
SergeHSergeH
3381214
add a comment |
I had a working iOS app with Jukebox music library and background audio. However, an hour after everything was working well, the app started to crash with
libc++abi.dylib: terminating with uncaught exception of type NSException
every time I close the app. Usually the music used to continue playing in the background, but now the app crashes. I also opened an old project that was only working well, but the same error came up.
The app works well in the simulator, but not on the device.
I didn't post any code because I literally didn't change things in the old project at least for it not to work anymore and crash. What should I do? The outlets are good btw.
EDIT
Here's the stack trace:
What's weird is that I tried the app on my friend's iPhone 6 running 12.1 and it worked with no issue, however when I do it on my iPhone 6S running 12.1 it crashes. What do I do in this case?
swift crash ios-simulator device nsexception
asked Nov 13 '18 at 0:13
SergeHSergeH
3381214
You should try to find out what that nsexception is ;)
– Mars
Nov 13 '18 at 0:19
@Mars Can you please help me? it’s really annoying that my app suddenly stopped working. I added the exception breakpoints, but they didn’t help as it directly points to AppDelegate when the crash occurs
– SergeH
Nov 13 '18 at 0:24
You need to show a stack trace or error message
– Mars
Nov 13 '18 at 0:48
But secondly, try googling the error message. I see a ton of possible solutions/causes HERE stackoverflow.com/questions/26442414/…
– Mars
Nov 13 '18 at 0:50
@Mars I added the stack trace. Another thing is that the app worked on my friend's iPhone, but not mine. How is that? I did a lot of research before asking the question on SO so i've seen the link you're re-directing me to
– SergeH
Nov 13 '18 at 8:48
add a comment |
I had a working iOS app with Jukebox music library and background audio. However, an hour after everything was working well, the app started to crash with
libc++abi.dylib: terminating with uncaught exception of type NSException
every time I close the app. Usually the music used to continue playing in the background, but now the app crashes. I also opened an old project that was only working well, but the same error came up.
The app works well in the simulator, but not on the device.
I didn't post any code because I literally didn't change things in the old project at least for it not to work anymore and crash. What should I do? The outlets are good btw.
EDIT
Here's the stack trace:
What's weird is that I tried the app on my friend's iPhone 6 running 12.1 and it worked with no issue, however when I do it on my iPhone 6S running 12.1 it crashes. What do I do in this case?
swift crash ios-simulator device nsexception
asked Nov 13 '18 at 0:13
SergeHSergeH
3381214
I had a working iOS app with Jukebox music library and background audio. However, an hour after everything was working well, the app started to crash with
libc++abi.dylib: terminating with uncaught exception of type NSException
every time I close the app. Usually the music used to continue playing in the background, but now the app crashes. I also opened an old project that was only working well, but the same error came up.
The app works well in the simulator, but not on the device.
I didn't post any code because I literally didn't change things in the old project at least for it not to work anymore and crash. What should I do? The outlets are good btw.
EDIT
Here's the stack trace:
What's weird is that I tried the app on my friend's iPhone 6 running 12.1 and it worked with no issue, however when I do it on my iPhone 6S running 12.1 it crashes. What do I do in this case?
swift crash ios-simulator device nsexception
swift crash ios-simulator device nsexception
asked Nov 13 '18 at 0:13
SergeHSergeH
3381214
asked Nov 13 '18 at 0:13
SergeHSergeH
3381214
edited Nov 13 '18 at 8:47
SergeH
asked Nov 13 '18 at 0:13
SergeHSergeH
3381214
asked Nov 13 '18 at 0:13
SergeHSergeH
3381214
asked Nov 13 '18 at 0:13
SergeHSergeH
3381214
3381214
You should try to find out what that nsexception is ;)
– Mars
Nov 13 '18 at 0:19
@Mars Can you please help me? it’s really annoying that my app suddenly stopped working. I added the exception breakpoints, but they didn’t help as it directly points to AppDelegate when the crash occurs
– SergeH
Nov 13 '18 at 0:24
You need to show a stack trace or error message
– Mars
Nov 13 '18 at 0:48
But secondly, try googling the error message. I see a ton of possible solutions/causes HERE stackoverflow.com/questions/26442414/…
– Mars
Nov 13 '18 at 0:50
@Mars I added the stack trace. Another thing is that the app worked on my friend's iPhone, but not mine. How is that? I did a lot of research before asking the question on SO so i've seen the link you're re-directing me to
– SergeH
Nov 13 '18 at 8:48
add a comment |
You should try to find out what that nsexception is ;)
– Mars
Nov 13 '18 at 0:19
@Mars Can you please help me? it’s really annoying that my app suddenly stopped working. I added the exception breakpoints, but they didn’t help as it directly points to AppDelegate when the crash occurs
– SergeH
Nov 13 '18 at 0:24
You need to show a stack trace or error message
– Mars
Nov 13 '18 at 0:48
But secondly, try googling the error message. I see a ton of possible solutions/causes HERE stackoverflow.com/questions/26442414/…
– Mars
Nov 13 '18 at 0:50
@Mars I added the stack trace. Another thing is that the app worked on my friend's iPhone, but not mine. How is that? I did a lot of research before asking the question on SO so i've seen the link you're re-directing me to
– SergeH
Nov 13 '18 at 8:48
You should try to find out what that nsexception is ;)
– Mars
Nov 13 '18 at 0:19
You should try to find out what that nsexception is ;)
– Mars
Nov 13 '18 at 0:19
@Mars Can you please help me? it’s really annoying that my app suddenly stopped working. I added the exception breakpoints, but they didn’t help as it directly points to AppDelegate when the crash occurs
– SergeH
Nov 13 '18 at 0:24
@Mars Can you please help me? it’s really annoying that my app suddenly stopped working. I added the exception breakpoints, but they didn’t help as it directly points to AppDelegate when the crash occurs
– SergeH
Nov 13 '18 at 0:24
You need to show a stack trace or error message
– Mars
Nov 13 '18 at 0:48
You need to show a stack trace or error message
– Mars
Nov 13 '18 at 0:48
But secondly, try googling the error message. I see a ton of possible solutions/causes HERE stackoverflow.com/questions/26442414/…
– Mars
Nov 13 '18 at 0:50
But secondly, try googling the error message. I see a ton of possible solutions/causes HERE stackoverflow.com/questions/26442414/…
– Mars
Nov 13 '18 at 0:50
@Mars I added the stack trace. Another thing is that the app worked on my friend's iPhone, but not mine. How is that? I did a lot of research before asking the question on SO so i've seen the link you're re-directing me to
– SergeH
Nov 13 '18 at 8:48
@Mars I added the stack trace. Another thing is that the app worked on my friend's iPhone, but not mine. How is that? I did a lot of research before asking the question on SO so i've seen the link you're re-directing me to
– SergeH
Nov 13 '18 at 8:48
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271962%2fios-app-crashes-when-closing-with-nsexception%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271962%2fios-app-crashes-when-closing-with-nsexception%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You should try to find out what that nsexception is ;)
– Mars
Nov 13 '18 at 0:19
@Mars Can you please help me? it’s really annoying that my app suddenly stopped working. I added the exception breakpoints, but they didn’t help as it directly points to AppDelegate when the crash occurs
– SergeH
Nov 13 '18 at 0:24
You need to show a stack trace or error message
– Mars
Nov 13 '18 at 0:48
But secondly, try googling the error message. I see a ton of possible solutions/causes HERE stackoverflow.com/questions/26442414/…
– Mars
Nov 13 '18 at 0:50
@Mars I added the stack trace. Another thing is that the app worked on my friend's iPhone, but not mine. How is that? I did a lot of research before asking the question on SO so i've seen the link you're re-directing me to
– SergeH
Nov 13 '18 at 8:48