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

pushToken is always null in IOS #884

Closed
Luckygirlllll opened this issue Oct 22, 2019 · 8 comments
Closed

pushToken is always null in IOS #884

Luckygirlllll opened this issue Oct 22, 2019 · 8 comments

Comments

@Luckygirlllll
Copy link

Luckygirlllll commented Oct 22, 2019

Description:

I'm getting pushToken null, when testing on real device in IOS

(your description here)

 onIds = async (device) => {
    console.log("push token", device.pushToken)
    }

push Token is always null inside onIds

Environment

  1. What version of the OneSignal React-Native SDK are you using? "react-native-onesignal": "^3.4.2",
  2. How did you add the SDK to your project? nom

Steps to Reproduce Issue:

  1. Add library
  2. Run app on real device

Anything else:

(crash stacktraces, as well as any other information here)

@Luckygirlllll
Copy link
Author

When I test the app from the TestFlight, it works correctly

@rgomezp
Copy link
Contributor

rgomezp commented Oct 22, 2019

Please reach out to our support channel at OneSignal.com for further assistance

@rgomezp rgomezp closed this as completed Oct 22, 2019
@hasgar-aot
Copy link

@Luckygirlllll @rgomezp same issue here.. any solution?

@Luckygirlllll
Copy link
Author

@hasgarAOT not yet, @rgomezp just closed my issue without any solution

@rgomezp
Copy link
Contributor

rgomezp commented Oct 30, 2019

Try pod deintegrate && pod install from within your ios directory. Also, can you please include logs? Make sure to run setLogLevel (onesignal function)

@hasgar-aot
Copy link

hasgar-aot commented Oct 31, 2019

My issue fixed after restarting. Maybe cache problem..i’m using 3.4.2

@rgomezp
Copy link
Contributor

rgomezp commented Oct 31, 2019

@hasgarAOT ,
Good to hear.

For others, please note that OneSignal is blocked by Egypt right now, which may contribute to occurrences of this issue.

@rgomezp rgomezp closed this as completed Nov 7, 2019
@hasgar-aot
Copy link

hasgar-aot commented Nov 21, 2019

@rgomezp same issue again.

These are the only warning I can find related onesignal:

[User Defaults] Couldn't read values in CFPrefsPlistSource<0x280fc0c00> (Domain: group.com.yepdesk.ydsaas.onesignal, User: kCFPreferencesAnyUser, ByHost: Yes, Container: (null), Contents Need Refresh: Yes): Using kCFPreferencesAnyUser with a container is only allowed for System Containers, detaching from cfprefsd

Attempted to send an event (OneSignal-idsAvailable) when no listeners were set.

It was working sometimes. I'm getting userId, but push token is null.
working with test flight builds
tried manual and pods
v3.4.2

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

No branches or pull requests

3 participants