Earlier it was working fine for both Android and iOS, but for the last few days only SHA1 is working for iOS. While validating the key it is returning "is Verified" as false. Whereas it is working perfectly for android devices.
Please help me out
Related
Sign in with Apple returns nonce on one device (iPhone X iOS 13.3.1) but not on others (iPhone iOS 13.3, iPad iOS 13.1.3, iOS 13.2.3). Based on the discussion at https://forums.developer.apple.com/thread/125419, it seems that all iOS 13 devices that are not updated to iOS 13.3.1 and that are using the native flow cannot use nonces. By native flow, I am referring to .
Note: the web flow works fine on the aforementioned devices. By web flow, I am referring to .
However, I am sure this cannot be the case, as Sign in with Apple works fine on PRE-iOS 13.3.1 devices with apps like Kayak (assuming Kayak uses nonces).
Why is nonce_supported: false being returned in the JWT from Apple?
According to https://developer.apple.com/documentation/signinwithapplerestapi/authenticating_users_with_sign_in_with_apple,
"nonce_supported
A Boolean value that indicates whether the transaction is on a nonce-supported platform. If you sent a nonce in the authorization request but do not see the nonce claim in the ID token, check this claim to determine how to proceed. If this claim returns true you should treat nonce as mandatory and fail the transaction; otherwise, you can proceed treating the nonce as optional." Do iOS 13 devices that are pre 13.3.1 just not support nonces?
I am implementing LinkedIn integration in my current iOS app and found that it suddenly stops working and found that SDK makes some changes. Please check this link:
https://developer.linkedin.com/blog/posts/2015/developer-program-changes
What is the solution to this?
I am currently working on adding Google App Indexing to iOS app.
(https://developers.google.com/app-indexing/ios/app?utm_campaign=app-indexing-ios-515&utm_source=gdbc&utm_medium=blog)
But it works only on one device - iPhone 4 (iOS 7).
On other devices [GSDDeepLink handleDeepLink:url] do nothing for the same url.
What can be wrong? And what is the difference between iOS 7 and iOS 8 for GSDDeepLink?
Thanx.
Please don't forget it's still "Limited Release", not everything is documented well probably. In "Introduction to App Indexing" page there is "Technical requirements" section, and they wrote :
Android:
Developed on apps with a minsdkVersion no higher than 17.
Available on searches using the Google app version 2.8+, and Chrome for Android 4.1+.
Available for signed-in users.
iOS:
Developed using a base SDK of iOS8. // Answer of your question maybe?
Available on searches using the Google app version 5.3+, and Chrome for iOS.
Available for signed-in users.
That means won't work in iOS7.
I have successfully integrated Google OAuth2.0 (version google-plus-ios-sdk-1.7.1) in my iOS application. The problem is my custom domain authentication works on iOS 6.1 but the same does not work for iOS 7.
Any clues? Thanks in advance.
Finally, I got the solution. The problem is simulator. Google OAuth2.0 not authenticating custom domain for iOS 7 simulator. This works perfectly on device.
A client just called us up and said all their YouTube videos in the App are no longer working. We haven't touched the App. This must have happened on February 28th, 2014. We had compiled this for compatibility mode so using iOS6 SDK when we submitted it in December, 2013. Now we can't see any YouTube working in the Simulator either. It's just crazy that YouTube and Google would pull the plug on people like this. We think that we have it working when using the iOS7 SDK but on devices only (simulator still doesn't work) so now we have to port the app to iOS7 only.
Is anyone else having this crisis?