I want to generate my build so that I have started following steps as like, I was doing from last few years. But this time following dialog box come in front of me while I try to export the build:
I have used Google for solution of this problem and tried multiple given suggestions but still I can't able to sort out this problem.
Here is the main reference that I found on stackoverflow:
code sign wants to sign using key - Doesn't allow or always allow but deny works
But those reply not working for me so please share your suggestion with me.
There may be something funny with the Trust setting in the certificate.
Open Keychain.
Find the relevant certificate in "My Certificates". Verify it hasn't expired.
Double click to open.
Doof with the When using this certificate field. Setting it to Always Trust before building might help. You can flip it back to Use System defaults after.
Also check the settings on the Code Signing specific field. That might be wrong.
This might have happened if you pressed "Deny" at some point in the past.
Related
I have been trying to generate an iOS certificate from the Codename One Control Center, launched from Intellij. Every time I submit my apple iOS developer credentials, and then input the 2 factor authentication code, it returns with this error:
REST request failed due to internal CLI failure. See server error log.c5307525-1805-4360-d4ca9d46cad0
I enrolled in the Apple Developer Program, and I believe I've agreed to all of the Apple Developer agreements and such, and I have exactly one device registered, as well as that one device set as the trusted device, so it receives the 2 factor authentication notifications. I'm also not sure where I am expected to be able to see the "Server error log" as I have searched around for that.
I've only been able to find 2 other cases that seem similar to mine but neither give me a clear idea of what the problem is or how to fix it. They do however seem to resolve their problems. I really don't have any more ideas as to what the problem could be.
Codename One IOS signing
Unable to Login to iOS Account from CodeNameOne
Another odd thing about this problem is that usually I get this error after being prompted to input the 2-factor authentication code, but sometimes I'm never prompted to input the code before getting the error, yet I will still receive the 2-factor authentication code text message on my phone despite there being nowhere to use it.
Any help is appreciated.
I have made some updates to the certificate wizard to try to work around this issue. Please give it another try. If you run into another problem, please post the error message again, and I'll look it up in the logs.
Ok so after looking around a bit further, I was finally able to find a git issue post that seemed similar to mine, and at the very end of the thread (linked below), someone mentioned that you need to be signed into that apple id on the device, not just have it as a trusted device. My iOS phone was showing up in the account because I was logged into the Apple Developer App, but this is not enough. Thanks for helping.
https://github.com/codenameone/CodenameOne/issues/2779
Following Apple's Password autofill guidelines with App Associated Domains here, I added the apple-app-site-association json file.
My app has that site listed as webcredentials:example.com. My app's bundle id is com.app.App which is listed as one of the apps under webcredentials.apps. The site has an SSL certificate.
In my iOS app I have an email text field with a content type of email (I've also tried username) and I have a password text field with new password (I've also tried password). When I select the email text field I get suggested emails. But when I select the password text field I get the same email QuickType suggestions and I get an error in the console:
Cannot show Automatic Strong Passwords for app bundleID: com.app.App due to error: Cannot save passwords for this app. Make sure you have set up Associated Domains for your app and AutoFill Passwords is enabled in Settings
I have AutoFill Passwords enabled on my device and I've proved that it does work on other apps.
I also never see in the logs that apple is calling my endpoint I provided above.
I verified that my Apple team ID is correct.
I've run out of ideas. Can someone else see what I'm doing wrong? Thanks!
Update:
It works fine on the simulator. The request goes out and the server gets it and it works. On the device it does NOT work.
I turned off the phone and turned it back on and it's working just fine... Really frustrating, I have no idea why it wasn't working, but I do know it was NOT making the network request from the device at all.
I turned off the phone I was testing with and turned it back on and that somehow fixed it... I have no idea why it wasn't working, but I do know it was NOT making the network request from the device at all.
I am wondering if I can use AutoFill without implementing the Associated Domains?
So this means for example that when the user register in my app that I save the credentials.
And then when he tries to login offer this credentials as AutoFill option.
Is something like that even possible to achieve?
As far as I can tell, you can take advantage of AutoFill without setting up associated domains. The part you'll miss out on is that iCloud/1Password/etc. won't be able to suggest the right log in details for your app without the associated domains set up. Instead, it'll prompt the user to choose/search for the matching log in details and select them from a list. But it should fill it in for you fine, especially if you add the extra details like setting textContentType on your text fields so iOS knows what's a log in form in your app.
ETA: Actually, I ended up having issues with AutoFill in my app that seemed to be fixed by setting up associated domains. The documentation makes it seem like that step is optional, but I had trouble where 1Password would let me choose the log in details but not fill them into the text fields until I had associated domains set up, whereas iCloud seemed to work fine mostly.
I'm working on a fingerprint Authentication using the keychain methods from iOS and can't manage to not show the pin proposal to be displayed after an error.
I'm using the flag kSecAccessControlBiometryCurrentSet which should only allow biometrics authentication.
So for the first prompt it works well and I didn't get the possibility to enter the passphrase but as soon as an authentication fails, the prompt changes and allow the user to enter his code. I would like to block this and only allow fingerprint authentification through that prompt.
There's the code I'm using: https://github.com/xavistas/cordova-plugin-touch-id/blob/noPinCode/src/ios/TouchID.m
If you have any idea, feel free to share :) !
I finally found the solution but it isn't really trivial.
You have to know that the keychain is never cleared for your application, even if you uninstall it.
So basically, if you tried one time to with a flag, let's say kSecAccessControlUserPresence, until you manually specify that you want to clear the keychain entry, this flag will stay stored.
And basically, even you if you "create the keychain token" each time the user connects to the app, it will not replace the keychain entry.
I hope it will help some of you !
Whenever i try to navigate to App-Specific Shared Secret within ItunesConnect the dialog box attempts to load briefly then I get directed to a crash page titled
"We can't process your request".
I've reset safari clearing all website data and also used other computers.
I've contacted Apple who are sending an email shortly requesting more information but wondered if anyone else had come across a similar fault?
Another very easy solution which worked for me:
Use safari
SOLVED
The problem was due to not previously having created a master shared secret.
Once I did this then I could generate the shared secret for the specific application.
I has a similar issue, when I was getting invited to join Apple Developer Program. I tried joining through the invitation link and I would always get the "We can't process your request" message.
The solution was to:
Log in to an iPhone/iPad with that particular Apple id.
Try to install an app.
You will get a terms and condition pop up that you should accept.
Install the app
Wait for a while until Apple fast servers update your status (around 1 hour for me)
Now you should be able to proceed without the weird message.
I think need to update Mac OS to latest will solve problem. Alternatively you can use google chrome browser.