can't get token registration on ios...
See original GitHub issueIm not getting the token registration in version 4.1.1, but yes in 3.10.2… idk why… its frustrating… the log not saying anything special… only in ios, android is working perfect…
`{
"description": "Demoapp App",
"license": "SEE LICENSE IN <your-license-filename>",
"readme": "application",
"repository": "<fill-your-repository-here>",
"nativescript": {
"id": "com.app.demo",
"tns-android": {
"version": "3.1.1"
},
"tns-ios": {
"version": "3.2.0"
}
},
"scripts": {
"tslint": "tslint -p tsconfig.json",
"ns-bundle": "ns-bundle",
"publish-ios-bundle": "npm run ns-bundle --ios --publish-app",
"generate-android-snapshot": "generate-android-snapshot --targetArchs arm,arm64,ia32 --install",
"start-android-bundle": "npm run ns-bundle --android --run-app",
"start-ios-bundle": "npm run ns-bundle --ios --run-app",
"build-android-bundle": "npm run ns-bundle --android --build-app",
"build-ios-bundle": "npm run ns-bundle --ios --build-app"
},
"dependencies": {
"@angular/common": "~4.1.0",
"@angular/compiler": "~4.1.0",
"@angular/core": "~4.1.0",
"@angular/forms": "~4.1.0",
"@angular/http": "~4.1.0",
"@angular/platform-browser": "~4.1.0",
"@angular/router": "~4.1.0",
"email-validator": "^1.0.7",
"nativescript-angular": "3.1.3",
"nativescript-fresco": "^3.0.4",
"nativescript-iqkeyboardmanager": "1.0.1",
"nativescript-ngx-fonticon": "^2.2.3",
"nativescript-permissions": "^1.2.3",
"nativescript-plugin-firebase": "^3.10.2",
"nativescript-social-share": "~1.3.2",
"nativescript-telerik-ui": "^3.0.4",
"nativescript-theme-core": "^1.0.4",
"nativescript-videoplayer": "^3.0.9",
"reflect-metadata": "^0.1.8",
"rxjs": "^5.4.0",
"tns-core-modules": "3.1.1",
"zone.js": "^0.8.11"
},
"devDependencies": {
"@angular/compiler-cli": "~4.1.0",
"@ngtools/webpack": "~1.5.3",
"babel-traverse": "6.24.1",
"babel-types": "6.24.1",
"babylon": "6.17.0",
"codelyzer": "^3.0.1",
"copy-webpack-plugin": "~4.0.1",
"extract-text-webpack-plugin": "~2.1.0",
"filewalker": "^0.1.3",
"lazy": "1.0.11",
"nativescript-css-loader": "~0.26.0",
"nativescript-dev-typescript": "^0.4.5",
"nativescript-dev-webpack": "0.7.1",
"raw-loader": "~0.5.1",
"resolve-url-loader": "~2.1.0",
"tslint": "^5.4.2",
"typescript": "~2.3.4",
"webpack": "~3.0.0",
"webpack-bundle-analyzer": "^2.8.2",
"webpack-sources": "~1.0.1"
}
}`
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
iOS-13 Unable to receive Device Token. - Apple Developer
After upgrade to iOS-13, we are unable to receive Device Token (intermittent) when we perform UIApplication.shared.registerForRemoteNotifications().
Read more >Device Token Registration is not working as expected #207
Integrate Braze through Cocoapods and register the device token data. Even tried the ff: Restart the phone; Force Restart the phone; Force exit ......
Read more >Correct way to retrieve token for FCM - iOS 10 Swift 3
The tokenRefreshNotification function doesn't always get called when ... First register for the firebase token refresh notification:
Read more >iOS token or Android ID registration failed for some device
Then, we checked in Audience -> Device Tokens / Android Channel IDs page and realized it seems that their device token / Android...
Read more >Send a test message to a backgrounded Apple app - Firebase
Add Firebase to your Apple project · Access the registration token · Send a notification message · Next steps.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi, We have the same issue. After some debug, the onPushTokenReceivedCallback and onMessageReceivedCallback are not fired.
this function retrieves correctly the token. So the init is done, and its not firebase communication issue with APNS.
and yes, its very frustrating 😃
The same has happened to me with push notifications. Completely agree with you. The idea of nativescript is good, but it’s all very poorly documented. Each step is a little hell until you get what you need.