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

[Bug]: EXC_BREAKPOINT fatal exception in OneSignalNotifications.m #1530

Open
1 task done
trooperandz opened this issue Dec 18, 2024 · 1 comment
Open
1 task done

Comments

@trooperandz
Copy link

trooperandz commented Dec 18, 2024

What happened?

An unhandled, fatal exception was thrown in the OneSignalNofications.m file with the following breadcrumb being reported in Sentry (also see image attached):

EXC_BREAKPOINT: Exception 6, Code 1, Subcode 4364248544

Screenshot 2024-12-18 at 3 55 53 PM

Steps to reproduce?

I am not able to create a reproduction of the error as it happens intermittently and I do not know of a reliable way to recreate it.

What did you expect to happen?

I expect the exception to be fixed or handled in some way instead of causing a fatal crash.

OneSignal iOS SDK version

Release 5.2.8

iOS version

17

Specific iOS version

* iOS 18.1.1
Note: I noticed that there is no 18x option above; is this due to official support or does the template need to be updated?

Relevant log output

system

    exception
        stack-trace
            frame (marked in-app by stack trace rule (family:native package:**/Containers/Bundle/Application/** +app))
                filename
                    <compiler-generated>
                function
                    value
            frame (marked in-app by stack trace rule (family:native package:**/Containers/Bundle/Application/** +app))
                filename
                    onesignalusermanagerimpl.swift
                function
                    OneSignalUserManagerImpl.createNewUser
            frame (marked in-app by stack trace rule (family:native package:**/Containers/Bundle/Application/** +app))
                filename
                    onesignalusermanagerimpl.swift
                function
                    OneSignalUserManagerImpl._login
            frame (marked in-app by stack trace rule (family:native package:**/Containers/Bundle/Application/** +app))
                filename
                    onesignalusermanagerimpl.swift
                function
                    OneSignalUserManagerImpl.user.getter
            frame (marked in-app by stack trace rule (family:native package:**/Containers/Bundle/Application/** +app))
                filename
                    onesignalusermanagerimpl.swift
                function
                    OneSignalUserManagerImpl.setPushToken

frame (marked in-app by stack trace rule (family:native package:**/Containers/Bundle/Application/** +app))

    function
        OneSignalUserManagerImpl.removeAlias

frame (marked in-app by stack trace rule (family:native package:**/Containers/Bundle/Application/** +app))

    filename
        osnotificationsmanager.m
    function
        +[OSNotificationsManager sendPushTokenToDelegate]

frame (marked in-app by stack trace rule (family:native package:**/Containers/Bundle/Application/** +app))

    filename
        osnotificationsmanager.m
    function
        +[OSNotificationsManager didRegisterForRemoteNotifications:deviceToken:]

frame (marked in-app by stack trace rule (family:native package:**/Containers/Bundle/Application/** +app))

    filename
        uiapplicationdelegate+onesignalnotifications.m
    function
        -[OneSignalNotificationsAppDelegate oneSignalDidRegisterForRemoteNotifications:deviceToken:]

    frame
        function
            UIApplicationMain
    frame (marked in-app by stack trace rule (family:native package:**/Containers/Bundle/Application/** +app))
        filename
            main.m
        function
            main

type

    EXC_BREAKPOINT

Code of Conduct

  • I agree to follow this project's Code of Conduct
@nan-li
Copy link
Contributor

nan-li commented Dec 21, 2024

Hi @trooperandz thank you for reporting this crash, we will investigate.

Yes we need to update our template to reflect ios 18!

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