I'm building a simple app, as it is described on this tutorial: Instagram like app
However, I've made all the steps correctly, to the "Run the app" part, but when I ran it, the Xcode 7 (swift2) outputs this error every time I launch the app or pull to refresh:
2015-09-20 00:46:41.224 Paws2[1196:393571] [Error]: unauthorized (Code: 0, Version: 1.8.5)
I'm using the latest pod available and I don't know how to bypass this issue.
Note that I've made an exactly app as described in the tutorial with the version 1.7.5 and the error was the same, so I updated the pos version to the latest.
I've names the app Paws2 on purpose, it wasn't a error, as it says in the Tutorial to name it 'Paws'.
Thanks in advance
- Regards, Ivan.
EDIT 1: I've updated cocoapods and everything else related and the error continues.
I had a same error too.
My case was silly. I put wrong Application ID / Client Key in didFinishLaunchingWithOptions method on AppDelegate.
[Parse setApplicationId:#“Your Application ID"
clientKey:#“Your Client Key"];
Make sure you put right keys.
Related
I'm in the process of updating projects to Swift 2 and iOS 9. One of the projects I'm doing relies heavily on Facebooks SDK. I use it to login, get user information, ect... Prior ot the update, once you logged in the Safari would redirect you directly to the app. Now I'm getting a fun little modal displaying the following (See Fig 1 at bottom)
I assume this has some connection to the new Info.plist key we add LSApplicationQueriesSchemes with a Item0 as fbauth2 now required by iOS 9.
I also noticed I'm getting a stack trace with my app saying:
failed for URL: "fbauth2:///" - error: "(null)"
I found the reoccurence of the new key data fbauth2 interesting, and I'm assuming that there is now a way to configure what this modal will say upon redirect. Does anyone have any idea how to configure this? I'm assuming this is a common issue for all those updating their apps. Thanks!
Fig 1
Make sure that you have updated to the newest version of the Facebook SDK at http://fb.me/FacebookSDKs-iOS-20150910.zip.
You will also want to Whitelist the Facebook Servers for Network Requests.
More information on this can be found here.
Specifically look at steps #2 & #3.
From the documentation in Step #3 there were also changes to the canOpenURL method:
Why do I see console messages like 'canOpenURL: failed for URL: "fb...://' or ?
This is an Xcode warning indicating the the canOpenURL: call returned false. As long as you have configured the LSApplicationQueriesSchemes entry in your plist as described above, you can ignore this warning
I am trying to use PayPalMPL 2.1.7 for iOS to accept third party payments in my app. When I use this code to initialize the environment:
[PayPal initializeWithAppID:#"APP-80W284485P519543T" forEnvironment:ENV_SANDBOX];
I get this error in the log:
Checking Error********************
Posting Error: -1
and this error as an alert in the app:
Error
internal server error
I would love to upgrade to the new PayPal iOS SDK, but it doesn't offer third party payments yet.
Any idea what will fix these errors?
Thanks!
However the question has an answer, I would like to add my two cents for future beginners like me who may found the same error.
Just add Bundle display name in your info.plist of your project as an empty.
Here's the screenshot.
Fixed this by adding Bundle Display Name in info.plist
I am following all the instructions here (i'm using Swift) without error. I can even build the project fine. When I connect my iPhone (5C) and try to run the app on the phone, I get the following error
Here's the error message in case it is not visible in the image:
Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-stdlib-tool failed with exit code 1
What am I doing wrong? I am using iPhone 5C for this.
hate to answer my own question but this issue is resolved now. I restarted the project completely and followed all the steps again, no issue anymore.
I'm trying to setup Parse crash reporting on iOS, using this guide, but unfortunatly, even after several crashes, there is nothing on my dashboard.
Here is my code (i'm using sdk 1.6.3) :
- (void)crash {
[NSException raise:NSGenericException format:#"Everything is ok. This is just a test crash."];
}
...
[ParseCrashReporting enable];
[Parse setApplicationId:#"********"
clientKey:#"********"];
[self performSelector:#selector(crash) withObject:nil afterDelay:10.0];
I followed the troubleshooting guide:
Make sure you've enabled Crash Reporting in your App Delegate before you initialize Parse. DONE
If you're testing, make sure Xcode isn't catching the crash with the debugger. DONE
Build, run, stop the app, and then run it from the home screen.
Crashes are sent on the next run of the app. Make sure the app isn't crashing again before it has a chance to send the crash information. If you're testing, you can ensure this by adding a delay. DONE
Crashes may take up to a minute to show up on the dashboard.DONE
Make sure you don't have any other crash reporting solutions linked to your application, as they might interfere with each other. DONE, (disable Flurry)
I tried on both simulator and device, as recommanded here.
Finally, i've this message in my console:
+[PFAnalytics trackEventually:params:]: unrecognized selector sent to class 0x10f08ac20
Any help is highly appreciated.
Parse must have a bug in v1.6.3 because I have downloaded v1.6.0 and it works all fine.
You can download it here:
https://parse.com/downloads/ios/parse-library/1.6.0
And this is the order for enabling:
[ParseCrashReporting enable];
[Parse setApplicationId:kParse_AppID clientKey:kParse_ClientKey];
This probably doesn't count as any answer but I don't have enough rep to comment.
Have you tried enabling the crash report AFTER setting up parse with your keys? I know this was an issue for me when I was trying to enable the local datastore.
I know it goes against the guide but weirder things have happened when I use Parse...
Parse 1.7.3 is also busted... upgrade to 1.7.4!! !
EDIT: DONT UPDATE TO 1.7.5 -- that seems to be busted too !!
Latest version Parse SDK 1.6.4 fixes this problem!
https://www.parse.com/docs/downloads
Anyone encountered this already?. I downloaded the sample code for IOS from github. I replaced the app id with my own, that i got after whitelisting my device. I ran the app and selected the device and media to cast. Soon after I hit the cast button, I am getting the following error....
Failed to start application (com.google.GCKFramework.GCKApplicationSessionError); caused by: entity not found (com.google.GCKFramework.GCKNetworkRequestError).
Found solution for this one. Once I enabled the Chromecast to send it's serial number to Google, the error went away (for future reference). It can be done in settings.
Source: https://github.com/googlecast/cast-ios-demo-player/issues/5