I am working on a project in Xcode using objective c. I am implementing kinvey for login purposes and found that there is an error when on login and registration, both manual and auto-generated, on the simulator. The odd thing is that the error only happens on iOS 8.3; it works fine on 9.0 or 9.3.
In 8.3 I receive the following error:
domain: #"KinveyError" - code: 406
#"Kinvey requires application/json as the Content-Type of the response"
I have tried resetting the simulator, restarting Xcode, restarting the mac, updating to the latest kinvey module, and even using an old kinvey module. The error persists, and I am not sure what else I should try.
Does the Statusshare sample app work for you?
Here is the link: http://devcenter.kinvey.com/ios/samples/statusshare
It does have new user account creation and login. I tried it on an iphone6/ iOS 8.3 simulator and Kinveykit version (1.40.7) and the sample worked fine for me.
Thanks,
Pranav
Kinvey Support
Related
Using the Airwatch SDK v21.4 on iOS an error is shown:
"We were unable to retrieve the configuration information. Press
continue to try again"
Using Airwatch SDK 20.9 worked fine, but after upgrading to version (21.0 thru 21.4) on iOS the SDK is displaying the error.
The message text can be found in an AWSDK.framework file Localizable.strings within the entry RetryToFetchConfigurationInformation
I can do a fresh install from the HUB app just fine.
After launching the app the UI is not displayed until a successful response from controllerDidFinishInitialCheck.
My controllerDidFinishInitialCheck method does not contain any errors.
After receiving a valid controllerDidFinishInitialCheck result the UI is displayed, followed by a popup alert message with the error.
Advice / Suggestions / How can I isolate this issue? It may be a timeout issue?
I've developed an iOS app that uses the url(forPublishingUbiquitousItemAt:expiration:) method of Apple's FileManager class. Starting with the first Beta of iOS 13 this function stopped working and now it throws an error, stating "This code has been removed. You should switch off of this SPI". But I can't find anything related to this function neither in the release notes of iOS nor in the documentation for this function, and it even states there that it would be supported on Mac Catalyst 13.0+.
This also has nothing to do with Xcode 10 and 11, as it occurs when the app is built using either one of those versions.
Does anyone of you know more about that? It would be great to get new information on that.
Thanks,
Fabian.
This is fixed in iOS 13 beta 6. Updated today and this error magically disappeared!
Had my mind blown when I saw this error message.
When I am clicking for generating OTP with signinwithphonenumber() method. Firebase returns "Error: An internal error has occurred." this error in some iOS devices. While in development it is working fine. But test flight build returns this error in some devices and working fine with other device. I have done coding in react-native.Can anyone please help me resolving this issue? It would be a great help.
Thank you.
I have been using FB iOS SDK 3.13.1 in my app and Login is working fine until I setup facebook account in Settings->Facebook. I couldn't login using FB at all. It was kept giving me error :The operation couldn't be completed (com.facebook.sdk error 2)
I tried all suggestions mentioned on stackoverflow. Changing facebook app settings or handle openURL but none worked.
But If I removed account from settings->facebook. Login worked. So I did setup all things correctly as instructed.
Not sure, what's wrong but I think FB SDK is very unstable.
Solved. after lot of searching and tries, I realized its just issue with Facebook ios SDK. Hence upgraded to 3.14.1 and its working fine. I even tried to reproduce the issue with an older build and try same scenario number of times.
I am using AFNetworking 1.2 library in my app. When I have iOS6 as a base SDK everything works fine, but if I change base SDK to iOS7, then receiving an error in some requests(not all) stating that - "The network connection was lost".
I am not able to find out the cause of the issue, also there is no pattern for this issue as all requests are not failing.
Is there something change in the iOS7 SDK which is causing this issue?
After analyzing issue for 2-3 days, found the root cause of the issue. In response header getting some field which sdk not able to handle.
As others have said, for iOS7, you'll want to upgrade to a newer version of AFNetworking (2.x)