When I tried uploading it I got the following errors
Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'com.apple.developer.icloud-containter-identifiers' in 'Payload/Appname.app/Appname' is not supported
Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'com.apple.developer.icloud-containter-development-identifiers' in 'Payload/Appname.app/Appname' is not supported
Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'com.apple.developer.icloud-services' in 'Payload/Appname.app/Appname' is not supported
Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'com.apple.developer.icloud-containter-environment' in 'Payload/Appname.app/Appname' is not supported
PLEASE PLEASE help. I have tried redoing the provisioning profiles and I am using key-value pair for iCloud. Seemingly simple stuff.
I have the solution for this (I am using Xcode 5.1.1).
I have uploaded a new version (1.1) of my existing app in which I have introduced an iCloud feature, which was not present on the previous version.
While uploading the build it showed the same error as yours (as seen in your question).
The solution is:
1- Open apple developer account.
2- Edit your AppID
3- Uncheck the iCloud container which you selected before.(While uncheck, iCloud will show configurable and leave it as "Configurable").
4- Edit your provision profile and download it again.
Open the provision profile and submit the build to the App Store.
Hope this works for you too.
I ran into this same bug/issue today. The fix almost worked, but interestingly when I set it back to "configurable", it added a *maps reference in my .info file! This of course created an error on a new Validate, which was unfathomable to me as my app DOES NOT use maps! I deleted the strangely added "maps" reference that was "created magically" by "unchecking" the iCloud container, and then the Validation went fine. Thanks!
Related
I added logo for my OAuth Consent screen and Google want to verify it. I tried to prepare it for verification but when I want to submit I am getting this information:
You need to set up an OAuth credential for this project before you can submit for verification
Ok, I go to credentials, click Create credential, I fill all forms and when I want to create I am getting this error:
The request failed because the Android package name and fingerprint are already in use
How to do it without removing API keys?
I will be glad if I could remove logo but I try to find how to do it and I found it's impossible without removing API keys.
As per the error you can’t have 2 projects of the same package name. If you want to delete the same also it takes a few days to get deleted fully from developers' console.
Try Below Solutions:
Solution 1 : Try to create a new project with a different package name.
Solution 2: Try to generate a new SHA-1 key by custom signing the application by generating a signed apk from the Android studio.
Please refer to the Signin APK for more information.
refer to this link we integrated CustomPermissionClaimHandler to our server without any errors but still we can't get the permissions of the users... I know how to create custom claims refer to this link and if I follow these 2 links' steps, I can create permission field like a textbox as shown on picture (testClaim and organizationID are examples about that from picture)... I thought that after integrating CustomPermissionClaimHandler I would see permissions like Role field as shown on picture with blue line but still it comes with empty textbox as shown on picture with green line. Is there any way to get the permissions?
EDIT: I can get JWT including my custom claims and if I decode it I see like this (as you see it doesn't contain permissions):
By looking at the JWT response, I can say you have done either or both of the following.
It seems there is a mistake in the guide of configuring the application-authentication extension.
If you have added,
[authentication.framework.extensions]
claim_handler="com.wso2.sample.claim.handler.CustomClaimHandler"
in to the deployment.toml, but you use the jar by building the code, there is a mismatch in the package name. You have to use the following config.
[authentication.framework.extensions]
claim_handler="org.wso2.custom.claim.PermissionClaimHandler"
Because of this configuration issue, your custom handler may not get executed even though that service got activated properly.
If the claim handler is active and the configuration is correct as step one, you might have missed something when mapping the custom claim to an oidc claim / adding it as an OIDC sope / configuring service provider claims
I created a new service account and I was trying to generate a key for it. I selected "Create Key", chose "JSON", and then this happens:
Download image
The download just doesn't happen (0kb size and host is null), I've tried on different browsers, different computers and I don't know what to do, the problem doesn't seem to be on my side...
What can I do about this?
I just had this same problem.
In order to access the Service Account Key file you need to ensure that you can use your API Key (under your Project Credentials), which may be restricted.
My API Key was restricted to my IP address and to the specific API I wanted to use.
After removing the API restriction only then did the download work (see below).
Hope this helps.
UI showing API restrictions removed
I also had the same problem but got solved by changing my browser.
Since I was working with the brave browser and was unable to download this file.
After that, I changed my browser to chrome. The problem was solved.
SOMETIME BROWSER CAN HAVE SOME ISSUE.
I'm setting up a 'Login with Facebook' button and have it on a test page. http://www.digitalinkmultimedia.com/my-account
I believe I have things set up correctly for the app at developers.facebook.com. The app says it's public and available. I'm using Business Catalyst as the CRM, and the facebook integration appears to be correct (App ID, App Secret, etc)
When I click the login with facebook button the first time I get the message about my profile info being shared....but when I continue I get a 'Facebook login is currently unavailable'.
One thing I noticed is that when the popup first loads the FBTOKEN parameter has a number in it, then it quickly changes to FBUTOKEN=00000000-0000-0000-0000-000000000000#=
Any suggestions would be appreciated.
In the Facebook developers console for your app, please go to App Review > Permission Feature and give Advanced Access for "public_profile" and "email".
Facebook Login of the iOS app is working well without the Advanced Access setting.
If you're experiencing this now (end of 2020) it might be due to a pending "Data Checkup":
As part of an ongoing effort to protect user data and drive long-term value for developers, Facebook has introduced an annual Data Use Checkup for app admins to certify that their API access and data use comply with Facebook Platform Terms and Developer Policies, together with all other applicable terms and policies.
Enter https://developers.facebook.com/apps and you should see your app in red color with a note that Data Checkup is due.
You'll need to spend a few minutes to fill in a simple form...
After you're done you should be good 👍🏼
https://developers.facebook.com/apps
https://developers.facebook.com/apps/395514758911597/fb-login/settings/
Get Advanced Access
I agree that any data I receive through public_profile will be used in accordance with the allowed usage.
download open ssl and paste in E drive create folder software--------
and extract here openssl
keytool -exportcert -alias androiddebugkey -keystore "C:\Users\USERNAME.android\debug.keystore" | "PATH_TO_OPENSSL_LIBRARY\bin\openssl" sha1 -binary | "PATH_TO_OPENSSL_LIBRARY\bin\openssl" base64
keytool -exportcert -alias androiddebugkey -keystore %USERPROFILE%.android\debug.keystore | D:\FbDependentSoftware\bin\openssl sha1 -binary | D:\FbDependentSoftware\bin\openssl base64
D:\FbDependentSoftware
password :- android
8Rc05yVGh4n4xVIx4lkfCYYrzrM=
For me #NajamUsSaqib's comment worked, tried getting advance Access for Email and Public Profile and it started working.
If anyone is still facing this issue. Please check in your developer account if you have a pending Data use Checkup.
Once you complete it, it should work.
I had the same problem and got fixed the following way:
Site Settings>Social Integration
on the field where it says "Enter Site URL of your Facebook application" make sure you have your address as follow:
http://www.example.com not http://www.example.com**/**
Basically it will not connect to your FB App if you have a " / " after your domain.
I have got the same issue.
Check the setup is done or not. If not then review all the points that need to add the data
make sure add icons and url properly
make sure add domain
make sure you have ask for the permissions that you need
add platform and hashkey for android correctly
Most important thing you need to work in live mode
After all the above setup you will get the success
Developers please go through with the latest doc there is a-lot of changes in doc while integrating the facebook login or graph api or instagram api's.
When posting an achievement with a user message it gives the following error:
{"error":{"message":"(#100) You haven't enabled User Messages for this action type (127701393971353) yet. Please update your Open Graph settings in the App Dashboard","type":"OAuthException","code":100}}
No clue where to enable that.
Managed to get access to the setting by modifying the url manually with the id.
https://developers.facebook.com/apps/your_app_id_here/opengraph/action_type/127701393971353/
In case this helps someone else, I had this issue. My situation was: I had a live app with an approved Open Graph action. I needed to release a new version of the app but I needed a new Open Graph action for this so the earlier version still worked until users upgraded to the new version. When I used the new Open Graph action, I got this error. My problem was that I had made a simple typo error in the bundle id of the new app version so it didn't match with the bundle id I had specified for the iOS settings in the Basic Settings page in the Facebook Developer app. The clue was that in the error given in the Xcode debug console, the app id didn't match up.