Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XCode 10 beta 6: Crash on quick reply from push notification #232

Closed
saitun opened this issue Sep 11, 2018 · 5 comments
Closed

XCode 10 beta 6: Crash on quick reply from push notification #232

saitun opened this issue Sep 11, 2018 · 5 comments

Comments

@saitun
Copy link

saitun commented Sep 11, 2018

Mixpanel pod version: 2.4.5
XCode: 10.0 Beta 6

This happens consistently when doing a quick reply through push notification. Below is the error message and a screenshot of the crash in XCode.

Thread 1: closure argument passed as @noescape to Objective-C has escaped: file /.../Pods/Mixpanel-swift/Mixpanel/AutomaticEvents.swift, line 289, column 77

screen shot 2018-09-10 at 4 34 24 pm

This is the stack trace which doesn't look very useful:

0    Mixpanel                           0x0000000104128e34 NSObject.userNotificationCenter(_:newDidReceive:withCompletionHandler:) + 944
1    Mixpanel                           0x000000010412986c @objc NSObject.userNotificationCenter(_:newDidReceive:withCompletionHandler:) + 180
2    UIKitCore                          0x000000022a5ba19c <redacted> + 3444
3    UIKitCore                          0x000000022ad88f04 <redacted> + 680
4    UIKitCore                          0x000000022ad88d04 <redacted> + 432
5    UIKitCore                          0x000000022adcc374 <redacted> + 220
6    UIKitCore                          0x000000022adcced0 _performActionsWithDelayForTransitionContext + 112
7    UIKitCore                          0x000000022adcc210 <redacted> + 248
8    UIKitCore                          0x000000022adc54ac <redacted> + 368
9    UIKitCore                          0x000000022a5d29c0 <redacted> + 468
10   FrontBoardServices                 0x0000000200a514bc <redacted> + 228
11   libdispatch.dylib                  0x00000001060a8dd4 _dispatch_client_callout + 16
12   libdispatch.dylib                  0x00000001060ac944 _dispatch_block_invoke_direct + 232
13   FrontBoardServices                 0x0000000200a8f618 <redacted> + 40
14   FrontBoardServices                 0x0000000200a8f12c <redacted> + 416
15   FrontBoardServices                 0x0000000200a8f8b0 <redacted> + 56
16   CoreFoundation                     0x00000001fdfb25a0 <redacted> + 24
17   CoreFoundation                     0x00000001fdfb24e0 <redacted> + 88
18   CoreFoundation                     0x00000001fdfb1d6c <redacted> + 176
19   CoreFoundation                     0x00000001fdfac8d8 <redacted> + 1040
20   CoreFoundation                     0x00000001fdfac404 CFRunLoopRunSpecific + 436
21   GraphicsServices                   0x000000020021d520 GSEventRunModal + 100
22   UIKitCore                          0x000000022a5a46d8 UIApplicationMain + 212
23   Embrace                            0x00000001026496bc main + 88
24   libdyld.dylib                      0x00000001fda6cc08 <redacted> + 4
@zihejia
Copy link
Contributor

zihejia commented Sep 13, 2018

hi @saitun, thanks for raising this! We will address all XCode 10 related issues as a high priority.

@zihejia
Copy link
Contributor

zihejia commented Sep 20, 2018

We have released 2.5.0 which supports Xcode 10. The issue could not be reproduced, however if the problem still exists, please reopen it.

@zihejia zihejia closed this as completed Sep 20, 2018
@saitun
Copy link
Author

saitun commented Sep 20, 2018

@zihejia Thanks for the update. I am however having problem installing the latest 2.5.0 version.

screen shot 2018-09-20 at 4 46 33 pm

@saitun
Copy link
Author

saitun commented Sep 21, 2018

Anyway I updated the pod by pointing to the latest commit and it works and I don't see the crash anymore. Thanks again.

@zihejia
Copy link
Contributor

zihejia commented Sep 21, 2018

hi @saitun , sorry about that, it's caused by the wrong tag in our end. I have fixed it now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants