We need our server to receive notifications about changes in subscription statuses.
To achieve this we followed the instructions from https://help.apple.com/itunes-connect/developer/#/dev0067a330b.
Our server supports App Transport Security (ATS) protocol. It was tested with this service https://apptransport.info/. So all requirements seem to be fulfilled.
We entered the target URL into the “Subscription Status URL” field. But we haven’t received a request (GET, POST, PUT) to the specified address after starting and expiring subscriptions in our sandbox.
Is there any way to troubleshoot this kind of problem?
Just finished resolving a similar issue after submitting a bug report. A different underlying problem, we were missing the intermediate CA on our SSL certificate. curl on macOS didn't alert us to the error, but curl on linux did. I wrote up a summary of the issue and how to test it here:
https://deciphertools.com/blog/subscription-status-url-not-working/
Apple support helped us to find out the reason of our problem.
We are receiving a 403 response for server notifications that are
being sent by the App Store.
So we should try it with curl before asking this question. Now we receive updates correctly.
Related
Our app working normally on Ipad and when subscribe and cancel subscription it ok, but no notification sent to our server !
I have filled the App Information with the our server Sandbox Server URL,
Our link look like this: https://api.example.com/api/apple-api/noti/v2
[We have read related questions]
We followed the documentation below:
https://developer.apple.com/documentation/storekit/original_api_for_in-app_purchase/subscriptions_and_offers/enabling_app_store_server_notifications
I think WWDC22 feature Request a Test Notification may help you.
ref: https://developer.apple.com/documentation/appstoreserverapi/request_a_test_notification?changes=_2
This feat request Apple to send a Test notification to your link. If you didn't receive, it may be a link error or App Store bug.(To App Store Bug, resave in the App Store Page may help sometimes)
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 sorry to public this problem, but I really can not resolve it. I only use NetowrkExtension-DNS Proxy in my app. I finish my app and its functions is normal according to https://forums.developer.apple.com/thread/81103 . But when i publish it by Testflight, there are some thing wrong. When I open proxy after installing my app by TestFlight, I don not see the alert of VPN Authorization and get error -- permission denied. I want to know why and how to resolve it. I am looking forward to your reply, thank you
As specified in the documentation:
DNS proxy providers are only supported on supervised iOS devices.
That means you can't publish the app trough TestFlight, the only way is to push the app on a Supervised device, one of the ways is to use an MDM solution (like SimpleMDM)
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.
I'm still new to iOS dev.
And I'm very, very new to whole APNS idea. I followed many tutorials, and didn't go so well.
I'd like to ask some questions.
Can I use same .certSigningRequest file for dev/dist/apns certificates? Does it matter if some of this certificates from this .certSigningRequest have been revoked?
When I export my key in keychain to .p12 file, can I use this one for both dev/distribute version?
If my server open port 2195, by giving .pem generated from above cer, my server should be able to send push message, right?
How can I unsubscribe/unregister from my device and/or from server/apns service? I mean when I need to remove, and try to build&run the code again.
4.1 How does
[[UIApplication sharedApplication] unregisterForRemoteNotifications];
really work? Does it tell apns not to send message/just turn it off? How can my server/provider know if device need to unsubscribe?
I find this tutorial really useful: http://www.raywenderlich.com/32960/apple-push-notification-services-in-ios-6-tutorial-part-1
And here some questions I have about what I encountered.
1. The sample app from the tutorial worked fine, using both my laptop & my server to send a message. But after a few days, it doesn't. (the response is still 'Connected to APNS Message successfully delivered', but the message never reach my device)
What could be the cause? My friend have revoked a dev cert? (I shared acc. w/ my friends) Or I reinstall the app? I also tried method unregisterForRemoteNotifications & register again, but nothing happens.
2. I also tried https://apphq.shephertz.com for a provider. This one requires .p12 key file in their format. (link) I have another project (this one is unity) register apns thru the app. It seems fine since I can see device token & user store in the web. But when I tried to send message, I got an error, like
iOS KeystoreException Device ID : <my-device-token> : Invalid keystore password! Verify settings for connecting to Apple... Does anyone know what this mean?
Sorry for my poor English.