Push Notifications and "ambiguous certificate name"

Solar2D General Questions/Discussion
#1

Another hair-pulling prevention tip -
When you’re doing push notifications, don’t actually install the certificate that you download for Push. If you do, it will likely have the same name as another certificate on your keychain, and cause code signing issues.

My google chrome is set to automatically open files I download so this caused me some headaches [import]uid: 32462 topic_id: 31084 reply_id: 331084[/import]

#2

This is an excellent tip, worth adding to push docs. Thank you :slight_smile: [import]uid: 52491 topic_id: 31084 reply_id: 124287[/import]

#3

You’re welcome. Try to do my small part where I can … lot of helpful folks around here :slight_smile: [import]uid: 32462 topic_id: 31084 reply_id: 124294[/import]

#4

You’re certainly doing that - awesome :slight_smile: [import]uid: 52491 topic_id: 31084 reply_id: 124467[/import]

#5

This is an excellent tip, worth adding to push docs. Thank you :slight_smile: [import]uid: 52491 topic_id: 31084 reply_id: 124287[/import]

#6

You’re welcome. Try to do my small part where I can … lot of helpful folks around here :slight_smile: [import]uid: 32462 topic_id: 31084 reply_id: 124294[/import]

#7

You’re certainly doing that - awesome :slight_smile: [import]uid: 52491 topic_id: 31084 reply_id: 124467[/import]