I want to release an update of my app with the new addition of an app clip. Apple states in their documentation
Safari's Smart App Banner and sharing via Messages is only available when the app clip is published in the App Store.
Is there any way to verify that the app clip via smart banner will definitely work once the update is available in the store? Otherwise I basically have to hope that everything was set up correctly which I just refuse to believe that's the case. Did anyone do this yet and can tell me how to verify everything will work as expected?
Related
I am new to app clip experience and currently struggling to deliver my demo app to my client with full app clip experience (including scan QR code to open app clip).
My question is that can we have scan QR code to open app clip card for testflight beta version? I tried to add an invocation URL for the specific testing build, but not working at all.
Here are things I have done so far:
Scan QR code is working as expected for local registered experience, which means you must have app clip cached in your device via building from Xcode
App & clip is submitted to Testflight for testing. I can see the open app clip from Testflight App, and my app clip works perfectly.
I did a set of configuration about aasa file, and I can see it is configured properly
Any help would be very appreciated.
For testers, they launch through Testflight. Documentation says:
Users don’t install App Clips, and App Clips don’t appear on the Home screen. Similarly, testers don’t install the beta version of your App Clip, and it also doesn’t appear on the Home screen either. Instead, testers launch the App Clip experiences you configure for testing through the TestFlight app on their device.
https://developer.apple.com/documentation/app_clips/testing_your_app_clip_s_launch_experience
Testers can configure a local experience and then launch the app clip in that way.
Testers can also configure a local experience to launch the App Clip you distribute with TestFlight. However, you must still associate your App Clip with your website. In addition, testers must launch the App Clip from an App Clip experience for testing you configure in App Store Connect at least once to ensure that the App Clip is cached on the device.
That same documentation mentions how to setup a local experience.
I added Apple App Clip but later removed it not yet needed. It was added "Advanced App Clip Experience", later deactivated, but when you bring the NFC tag to the phone, an alert still pops up with an empty content and message "This app clip is not currently available in your country or region".
Deactivated Advanced app clip in App Store Connect
Expired all builds in TestFlight, which contain App Clips
Everything in app association file, domains for app clips, etc - removed
So why NFC scanning still present App Clip, but not redirect me in app/safari as earlier?
I had the same problem. The fix was to ensure that the App Clip Experience was deactivated in App Store Connect.
I submitted a binary/build that contained an App Clip to Testflight so that I could access the Advance App Clip settings.
Deactivated the App Clip Experience (your step #1)
Waited a day to account for the caching system, and now, after testing, scanning my QR Code (in your case, it would be triggering the event with the NFC tag) produces the correct results.
It is important to note that even though you may have a live app that does not contain an App Clip, you must still deactivate it in Advance App Clip.
I'm currently working on a small app to demonstrate the usefulness of iOS 14's new App Clips. Since this is a proof of concept to demonstrate the power of App Clips, rather than an app meant for production, I do not have an app available on the Store.
Is it possible to configure an App Clip launch experience without having an App available on the App Store? The documentation I could find appears to require the creation of an App Clip on Apple Connect.
Without an app in the app store you can create an app clip that can be used in a very limited way. If a proof of concept is what you're after, maybe the app clip testing methods will do.
Generally there are 3 options:
Run the app clip project in Xcode. add the environment parameter _XCAppClipURL to simulate the invocation link.
Use the local experience. Create a local experience on the iPhone you'd like to simulate the app clip on. Then invoke the app clip using a QR scanner or whatever other method you'd like to use. You'll need to configure this for each device you want to use the app clip on.
Use TestFlight. For this you'll need to upload some app and the app clip to app store connect (The build is for an app and app clip together). You don't have to submit them to the store, uploading the build to app store connect is enough to get them on TestFlight (at least for closed testing).
more information can be found in Apple's documentation
I have submitted my app for iPad only on app store. Is it possible to revert it to universal allowing to downloads on iPad as well as iPhone without resubmitting.
I did some googling but couldn't find anything useful.
FYI: It an app created using meteorJs
No, you will need to submit an update to your app in the App Store as the app type is embedded in the file you submit.
Apple will need to review your changes (i.e. Validate that it works correctly on iPhone).
I am building an album app. I want to set a photo in my own app as wallpaper. Is there some method available for doing so?
update:
I know there are already some similar questions posted. But they are out of time. So I am wondering if there is some method in iOS7 to implement so.
For apps going into the app store this isn't possible. Apps can't change anything outside of their environment this is because apps on iOS run in a sandboxed mode so they don't know anything about other apps that are on the device and can't affect the OS directly.
To actually do it you would probably need to use some private API so your app would get rejected under:
2.5 Apps that use non-public APIs will be rejected
but I suspect that they would actually reject it under:
10.4 Apps that create alternate desktop/home screen environments or simulate multi-App widget experiences will be rejected
As you are directly altering the home screen.