When a user installs my app one of the first questions is the "Trust Certificate" question. The user can select "Yes, this time", "Yes, always" or "No" Regardless of the option clicked the code continues on its merry way ...
Can anyone give me a pointer as to how I would catch the users response and act accordingly in my code.
thanks
So I found the answer for anyone who may need to know:
Using a Try/Catch within the VB.NET script does not return an error when the user disallows access. However using an OnError will catch an error of "Access Denied".
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
I am attempting to submit a new iOS app to Apple that uses "Sign in with Apple" to authenticate users. In all my local testing, this works perfectly.
During Apple's review process, they ran into an error and provided this screenshot:
Unfortunately, the error message is in Chinese, but Google Translate say it means "Incomplete registration".
The weird thing about this is that the error message is in place of where there should be a button. Here is how the screen looks when I try it:
Does anyone know how to get into this state where there is an error instead of a button to continue with the sign-in process?
Is it possible that this is human-error on the part of the reviewer, and they for some reason don't have the Apple ID account setup correctly on the device?
I'm not sure if it is relevant, but I am using Firebase authentication to handle the sign-in process. It appears from the screenshot that this occurs before any requests are made to the backend though.
Update:
I found another question that has a similar error message in English. It may be related to my issue, but I have been unable to reproduce this error by using an incorrect Bundle ID as the accepted answer suggests. I just wanted to add this info, as it may have some relevance.
I don't currently have a physical iOS device to test on. Is it possible that this error is only displayed on real devices or only when using a signed .ipa?
Update - App was approved:
I resubmitted my app for review and it was approved, so it seems that human-error or some glitch in Apple's process caused it to be rejected initially. Although my problem is solved, I still have no idea how the reviewer managed to get into the state displayed in the screenshot.
The "Sign-Up Not Completed"/未完成註冊 may be caused by using + signs instead of encoded spaces (%20) in the URL when you redirect to https://appleid.apple.com/auth/authorize
Source: https://forums.developer.apple.com/thread/122458
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.
As the title suggests, I'm having an issue with the method ACAccountStore requestAccessToAccountsWithType:options:completion. I expect this method to only prompt the user for permission the first time it is called for my app, but it is being shown every time.
Is there some way of checking whether the user has granted permission so I don't have to request it? Or is there some other kind of magic that will stop this behaviour?
I find this very odd, since in an earlier version of the same app, the behaviour was as I expected - it only prompted for permission on the first call.
Answering my own question. Hopefully somebody will find this useful some day.
What seemed to be causing the problem was a mismatch between the permissions available to my app, in particular the basic read permissions, and the permissions I was requesting. While my app's Facebook page showed 'email' as a basic read-permission, it was requesting 'basic_info'. Once I changed the permission to 'email', the app asked once and didn't do so again.
Users can post messages on Facebook using my application. iOS presents the users with the permission dialogue the first time they try to post ("foo app would like to post privately on your behalf" - Don't Allow / OK). Now it seems that this decision is a persisting one. Once this dialogue is completed either way, the user will never be asked again.
Now, as this might have happened out of mistake I don't think this is good enough for the user. Is there a way to initiate this permission dialogue from code somehow?
No. You can create your own dialog telling the user that they must go to the Settings app to change the privacy settings.