Submitted actions for google production review and it has been approved.
Then I invoked the action but still, it is prompting "Getting the test version of *****" as the initial response and then the welcome message.
Please provide the solution.
This is just happening for you, and possibly for anyone who is in the Alpha or Beta channels.
You can go into the simulator and indicate which version you want to use. This will apply for both the simulator and devices linked with the same account. If you have the new simulator, you can select "Settings"
then select which version you should use from the dropdown.
Alpha and Beta channel users can go to the same URL they used to connect to the channel and indicate they want to switch to the production version.
Related
App is built in flutter using Firebase authentication. When Apple review team tries to sign in by using provided testing phone number and they always stuck at reCaptcha based authentication screen. They are seeing attached screen forever.
App store rejected by giving reason:
Hello,
The issues we previously identified still need your attention.
If you have any questions, we are here to help. Reply to this message
in App Store Connect and let us know.
Guideline 2.1 - Performance - App Completeness
We discovered one or more bugs in your app.
Specifically, your app still displayed error message when we tried to
login.
Please review the details below and complete the next steps.
Review device details:
Device type: iPhone
OS version: iOS 15.5
Next Steps
Please run your app on a device to reproduce the issues, then revise
and submit your app for review. If at first you're unable to reproduce
the issue, try the following:
For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce.
For app updates, install the new version as an update to the previous version, then follow the steps to reproduce.
If we misunderstood the intended behavior of your app, please reply to
this message in App Store Connect to provide information on how these
features were intended to work.
Resources
For information about testing apps and preparing them for review, see Technical Note TN2431: App Testing Guide.
To learn about troubleshooting networking issues, see About Networking.
Please see attached screenshot for details.
Issue faced by Apple Review Team
I have tried following things:
https://firebase.google.com/docs/auth/ios/phone-auth#set-up-recaptcha-verification - As per this link i have done same configuration in Xcode, Put my REVERSED_CLIENT_ID in the URL schemes,
iOS URL Scheme in xCode
Also I have done APNs authentication key at firebase side,
Firebase APNS Configuration
However, I am unable to reproduce this issue at my end. But though, I tried all the possible solution based on answers on the SO. Still issue doesn't resolved for them.
Please let me know if am I missing some configuration?
Have you tried this?
Go to your firebase Project settings => App Check => Apps
Register your apps for app attention.
Issue I am facing is this below:
"We found that your in-app purchase products exhibited one or more bugs when reviewed on iPhone running iOS 14.2 on Wi-Fi."
"When validating receipts on your server, your server needs to be able to handle a production-signed app getting its receipts from Apple’s test environment. The recommended approach is for your production server to always validate receipts against the production App Store first. If validation fails with the error code "Sandbox receipt used in production," you should validate against the test environment instead."
I have implemented in-App Purchase (Non-Consumable), Its working perfectly fine in Buy and Restore etc. Apple Rejects with the above reason.
What I am doing:
Using SwiftyStoreKit
Click Buy Button
SwiftyStoreKit.retrieveProductsInfo
SwiftyStoreKit.purchaseProduct
On Success ( SwiftyStoreKit.finishTransaction )
Restore:
Click Restore
SwiftyStoreKit.restorePurchases
Please let me know if need more information or code etc and what I am doing wrong which rejected the app.
Apple Recently Replied me as well this below message:
"Regarding purchasing in-app purchases, we continue to be unable to buy the full version of the app. When we tap on the button to buy, the app continues to load indefinitely.
We are not able to provide feedback on app concepts or features, but we recommend evaluating your suggestions against the App Store Review Guidelines, as well as the iOS Developer Program License Agreement (PLA), and the iOS Human Interface Guidelines."
So I found the Solution for this. When ever you receive error something like above, here are the steps you need to check and do.
Check first your In-App Purchase Implementation. Are you doing it correctly, ending the transaction etc.
Check what is the latest version of iOS supported by your XCode. If its lower than the shown in the issue like in mine ( xcode ios version was 14.0 and issue with 14.2).
For that you need to just download the latest XCode which support that iOS Version and make a build and then submit for review. It will surely work.
I have deployed a flutter app on the google play as a production mode, which is this link, https://play.google.com/store/apps/details?id=yurikanamba.lovealapp
(sorry the social login doesn't work now)
I can see the latest update from the link, like screenshots, but I can still see the word (beta) right next to the app name like this.
I sent this link to some of my friends, but they cannot see the (beta) like I do.
Do you know why I can see that and how to get rid of the (beta) right next to the app name?
I guess I should disable the Beta project in our App releases on google console, but there is nothing I can deactivate my beta release...
I have got the same problem:
First I published my app as a public beta version then I released it to production track. However, when using my developer profile I'm still seeing this Beta title.
I have a tried to unregister from testers list, then cleared my browser cache (desktop and mobile), my Google cache but I'm still seeing it.
Try this anyway, it might work for you.
The only solution I found is to use another account that was not listed as beta tester, but it seems that for profiles who have been (or still are) beta testers, "Beta" won't go away from your app title.
I'm currently developing an action with Dialogflow.
As my development is stable enough to be tested, I released it as an Alpha Release and also shared it with some alpha testers.
Since the beginning, I released 10 (alpha) versions: new intents, account linking integration, but mainly Directory information changes, with a nice logo, description, privacy policy and so on...
My problem
Most of my alpha testers don't have access to the latest released version.
Actually they all have access to different (random?) previous versions of my action.
Even following the provided Opt-in link doesn't display the same version of the action (different Directory information).
I'm getting crazy, I tried removing everyone, published a new version, added all my testers back again... but it didn't help.
I think there's something I didn't get about Alpha Release...
Thanks for your help.
An additional question: do the testers have to click the Opt-in link, or should they be able to invoke my action from their Google Assistant app as soon as they're added as testers ?
Partial answer... I don't know about the different alpha versions but I can answer your question about the Opt-in link...
My limited experience tells me they need to accept the Opt-in link. When an alpha-tester tried invoking my Action prior to accepting the Opt-in link, they just got "related" web results. Immediately after accepting the Opt-in, they were able to invoke my action from their Google Assistant.
I recently changed the following things on our Apple Dev portal. I asked this before but wasn't very clear on what I had changed.
I'm using:
- Phonegap 2.1.0
- iOS 6 min 4.3
- XCode 4.5
I am using only development certificates for testing. We aren't testing the production certificates yet.
App ID's : Enabled Production Push notifications.
Provisioning: Added a distribution entry and removed 1 device from the profile.
I also changed the Product/Bundle Name in the main target.
I downloaded the new certificates and installed them.
I get a token perfectly, it registers for notifications. I don't get an error from Apple feedback. Is there anything that I changed that would effect push notifications? Would I ever have to re-download anything but the provision profile after making changes? I'm testing on an iPhone 4, I've rebooted several times and switched notifications on/off.
I also added the AppStore build scheme if that has any effect.
Well they started working after I changed the Bundle Display name back to the original name, but I don't think that's what fixed it, I had done that before.