Followed the quick start guide and get the above error when i try to load the app onto the phone.
Urban Airship Implementation Error - The AirshipConfig.plist file is missing and no application credentials were specified at runtime.
Didn't find what you were looking for?
New post-
Sean Conlin
Hi Rob,
This is Sean with Urban Airship Technical Support.
Everything related to the AirshipConfig.plist file is in Step 6 of the Quickstart guide.
Specifically, did you download the file and copy it into your project by dragging the file into Xcode?
Thank you,
Sean Conlin
Urban Airship Technical Support
Portland, OregonComment actions -
Hi Sean
Yes I followed Step 6 of the QuickStart quite. The file is in the solution, but it does not seem to get copied to the device. I am using the latest Xcode as i have iOS 9.3 on my phone.
Comment actions -
This is the read out from the debug area
2016-03-27 20:30:49.588 AppName[3624:1463518] [W] -[UAConfig validate] [Line 228] Development App Key is not valid.
2016-03-27 20:30:49.589 AppName[3624:1463518] [W] -[UAConfig validate] [Line 232] Development App Secret is not valid.
2016-03-27 20:30:49.589 AppName[3624:1463518] [E] -[UAConfig validate] [Line 244] Current App Key (Your Development App Key) is not valid.
2016-03-27 20:30:49.589 AppName[3624:1463518] [E] -[UAConfig validate] [Line 249] Current App Secret (Your Development App Secret) is not valid.
2016-03-27 20:30:49.589 AppName[3624:1463518] 🚨Urban Airship Implementation Error🚨 - The AirshipConfig.plist file is missing and no application credentials were specified at runtime.
fatal error: unexpectedly found nil while unwrapping an Optional valueThis is frustrating as the app works perfectly in the development version. Any suggestions?
Comment actions -
So after much searching on the website, I decided to try a few things, I found that by setting and adding the following to my AirshipConfig.plist
<key>detectProvisioningMode</key>
<false/>
<key>inProduction</key>
<true/>The build works and creates a device token.
Comment actions
Please sign in to leave a comment.
Comments
5 comments