Skip to content

Conversation

@Avery246813579
Copy link

It took me hours to figure out why I was getting BadDeviceToken in production while on my test iPhone everything was working great. I had to go to the node-apn package to figure out I needed production to be true inside the apn settings. The weird thing is, this was never said ANYWHERE inside the readme.

The production setting should be displayed on the readme (like the node-apn readme) so people can see they have to toggle it.

It took me hours to figure out why I was getting BadDeviceToken in production while on my test iPhone everything was working great. I had to go to the node-apn package to figure this out. 

The production setting should be shown in the settings (as it is inside the node-apn readme) so people can see they have to toggle it.
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 08793e7 on Avery246813579:patch-1 into 8035461 on appfeel:master.

@alex-friedl
Copy link
Collaborator

Hello @Avery246813579,
thank you for your suggestion!

I like the proposed change to add the production key to the README. But the additional sentence in the description is not entirely correct in my eyes. For integration environments it could make sense to leave the value at false if you choose to test against Apple's sandbox environment.

Could you change the explanation to simply explain that production=false will connect to the sandbox environment and production=true will result in connecting to the production environment?

keyId: 'ABCD',
teamId: 'EFGH',
},
production: false,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe add an explaining comment here and remove the comment down below?

@alex-friedl
Copy link
Collaborator

Closed in favor of ad1c566

@alex-friedl alex-friedl closed this May 3, 2018
@Avery246813579 Avery246813579 deleted the patch-1 branch May 4, 2018 01:59
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

Successfully merging this pull request may close these issues.

3 participants