Usually my target url is alway myprojectid.appspot.com but just about some minutes ago I needed to push an update but i'm getting another target url of myprojectid.uc.r.appspot.com
Please see the image below because I had to abort the process.
How do i fix this?
This is an expected behaviour, as seen here. You can also see the changes made in the releases notes for Google App Engine where it explains that App Engine is now changing the URLs that you use to send requests to your apps.
As stated in the release notes:
For example, an app can receive requests at https://PROJECT_ID.REGION_ID.r.appspot.com. This new URL is optional for existing apps, and will soon be required for all new apps.
If you are trying to deploy a new Google App Engine application, the URL will be the one you are seeing here https://PROJECT_ID.REGION_ID.r.appspot.com.
I hope it helps.
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.
I've managed to get both an iPad and iPhone hooked up to xcode, and can successfully deploy to the device. For some reason I'm getting network errors every time I try an access a feature that requires the internet, so I think there must be some setting in XCode I'm missing.
Do I need to specifically tell xcode that I permit the device to access the network?
Turns out it was an issue with PhoneGap (used to create cross-platform apps by using HTML5).
The error I was getting was similar to this:
SampleApp[549:17803] ERROR whitelist rejection: url='http://code.jquery.com/jquery-1.6.4.min.js'
And the solution can be found here:
http://www.anujgakhar.com/2011/11/22/phonegap-gotcha-error-whitelist-rejection/
"In your PhoneGap.plist file, you need to add the allowed URLs to the ExternalHosts array. I added “*” as I did not want to add each individual URL separately to the list but that’s your choice."
Is there any provision in iOS wherein the referral parameters used to start the iTunes application are passed on to the application on its first run?
For example in Android, if I use a link such as http://market.an......com.company.pany&referrer=heythere to download an app on Android and actually install the app, the Market app passes the "referrer" parameter and its value to the app on its first run, which the app can use to any extent.
Is there a similar provision in iOS?
We also struggled with this when we built our last mobile app, Kindred Photobooks. The best way we found is to basically bundle that information in the link and use fingerprinting to make that data available after install, which is working really well.
You can try to build fingerprinting in in house. Basically the steps would be the following:
1. When a link gets created, appending parameters to the link, or create a link reference in some backend database if you want shortened links
2. When a user clicks on that link, collect a fingerprint of their device from everything you can read in the browser (for example: IP, OS, screen size, etc) and redirect that user to the app store.
3. When the app opens, create a similar fingerprint from the same parameters collected in app, and match it up in your database to the outstanding fingerprint.
4. If there is a match, you can return those link parameters to the app through install.
Alternatively, if you don't want to build all that infrastructure and handle the many edge cases, we bundled it up into a free service called Branch. Check it out at http://branch.io
No, there is no such thing on iOS. But you can and should file a feature request at bugreport.apple.com, if you really need this feature.
As of iOS6, if someone installs your applications via a smart banner, you can pass a url to your app on startup. You do this by using the app-argument parameter:
A URL that provides context to your native app. If you include this, and the user has your app installed, she can jump from your website to the corresponding position in your iOS app. Typically, it is beneficial to retain navigational context because:
It should work on install:
When the app finishes downloading [after clicking install on an app banner], the View button changes to an Open button, and tapping the banner will open the app while preserving the user’s context from your website.
More here: http://developer.apple.com/library/ios/#documentation/AppleApplications/Reference/SafariWebContent/PromotingAppswithAppBanners/PromotingAppswithAppBanners.html
I think this will work (but the jury is still out: Does app-argument on Apple Smart Banner get passed to app on install? ), but testing this is tough: How to test Smart App Banner Urls on in Dev environment
No, AppStore doesn't pass any parameters to application - it just unzips ipa to application folder (container).
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
When my iPhone application start, I want to notify the user if there is a new updates / version released on App store.
Does anybody have any ideas or has anybody else achieved anything similar?
Thanks
Use Nick Lockwood's iVersion library. It's whole purpose is to notify the user when new updates are available.
iVersion is a library for dynamically checking for updates to Mac/iPhone App Store apps from within the application and notifying users about the new release. It can also notify users about new features in the app the first time they launch after an upgrade.
Purpose:
The Mac and iOS App Store update mechanism is somewhat cumbersome and disconnected from the apps themselves. Users often fail to notice when new versions of an app are released, and if they do notice, the App Store's "download all" option means that users often won't see the release notes for the new versions of each of their apps.
Whilst it is not permitted to update an App Store app from within the app itself, there is no reason why an app should not inform the user that the new release is ready, and direct them to the App Store to download the update.
And if your app is not on the App Store, either because it's an in-house/enterprise iOS app, or a Mac app delivered to customers outside of the store, you can't use the App Store update mechanism anyway.
iVersion is a simple, zero-config class to allow iPhone and Mac App Store apps to automatically check for updates and inform the user about new features.
iVersion automatically detects when the new version of an app is released on the App Store and informs the user with a helpful alert that links them directly to the app download page.
Or if your app is not on the store, iVersion lets you specify a remote plist file to check for new releases, and a download URL where users can get the latest release.
iVersion has an additional function, which is to tell users about important new features when they first run an app after downloading a new version.
These excerpts were taken from the Github page here, where you can download it. There is also a comprehensive tutorial on installing and configuring iVersion, so I recommend that you check it out.
Hope this helps!
To give a comprehensive answer. There are basically two ways you can go here. Depends on where you want to put the responsibility.
App checks for new versions on server
Using this approach, you would add a method to your app that is being called on every launch to compare the current version of the app (wherever you want to save that) with the version stored on the server. To achieve this, the server must implement a small web service that returns the latest version as a string or something else very simple. No rocket science there.
Server pushes new version information to app
This way you implement more code on the server-side to do a Push Notification to your app which informs the app about the new version. Advantage here is: Less client-side code and less effort to check, because the version check does not happen every time the app is started but instead only once the new version is actually released.
you can do a call to your server when the app starts.
and that way check for a news item in your database, for example.
When the server gives you something. show it in an alert.
On the other hand, when there is an update in the appstore, doesn't the iphone give a warning?
APNS - Apple Push Notification System
Try it and google for ready server solutions.
Update: Okay, lets get it longer -
APNS is the best way to inform user about something new. It works with every state of the app - even when app closed - and it helps to avoid unnecessary requests to server.
But you will need server to send pushes - if you can write it by yourself - it's nice, but the are some services to create backend for your app (no links - no ads, just google it).
To find out how to start with APNS on the client side and how to create all needed certificates and keys read this one
Just check the latest version by communicating with your server and compare with the current version of app when the app starts up, if there is a newer version, notify the user.
Apologies in advance for the plug - but I think a service I built extending the concept from my experience building many apps solves this problem. Look at CleverStork - an Update Manager for Apps
There is something known as Silent notifications from iOS 7 and above, you can use that for
this
We had submitted/distributed our application using wild card bundle identifier.
For Example :- 48NPCXXX.in.co.xyz.*
Now we are publishing an update version of the application with push notification feature.
How we can publish the update version with wild card appID.
Or we have to publish as new application.But in this case how old users
get notified of the updates.
We followed the instruction given in below link but it does not work for us.
http://developer.apple.com/iphone/library/qa/qa2009/qa1680.html
Look forward for quick reply.
The steps in that document are what you need to follow. Whoever has the current version of the app installed will be notified through the AppStore that there is a new version available and they can update it just like they would normally. You just have to follow the steps to make sure you don't have the wildcard appID and that you have all your notification certificates correctly registered.
It seems QA1680 has been removed. This looks like it might be its successor.