Background
I've been working on a react native app that uses expo to build and deploy the application to both stores.
Today I came across quite an amazing feature in expo. The publish button inside the gui actually pushes all of the changes you have made to every user of your app. There is no need for building and jumping through all of the hoops that Apple & Google makes you do.
Question
Since these changes can be basically full new versions of the app and no one at Apple/Google has checked them does this break the terms of service with Apple? They cannot monitor your newest release changes.
When choosing an app rating just set "unrestricted web acces" to true, that should be it
Related
I have an iOS app published in store, made with React-Native. (it is created by other developer, i'm not the original developer in this project.)
Now i'm refactoring my application into SwiftUI.
Is it possible to change entire project in same package? I want to keep app store page of my application.
I read how to publish applications. I read how to manage app package uri.
Yes, possible.
Keep your bundle identifier same and Increase your app version.
It is completely possible. You need to re-submit the updated app for review and approval by Apple.
Be sure that the bundle identifier is the same, otherwise it will be treated as a new app and will not replace the old one on the App Store page.
There are already many examples of companies that have completely changed the codebase of their apps.
I've to create a mobile app for my small company (150 users).
They use both Android and IOS device, and the only native feature I need is Notifications Push..
Cause of the notifications, I can't go pwa (ios doesn't support), so I would try react native app.
This app is for private usage, so I can't deploy it via App Store, but I can use the "enterprise program".
The problem is the price.. It Will cost 300$ every year, for only one app ?
I think I can leave the program once upon a time the app is deployed.. But have to subsribe when I'll have to update..
I've see the OTA possibility. Do you think I can deploy and Update via OTA (Codepush)?
Thank you
Have a look at Expo, it might be just you need. Comes with push notifications support out of the box, the pre-release/beta development/distribution experience is just beautiful. One-click update (without any OTA settings, configuration, hassle) of your app's JS bundle, QR code sharing, and lots more.
Also, you can use TestFlight (together with Expo) if you guys don't want to pay for anything, but that app will expire after 90 days (and you'll have to re-submit a build every 90 days).
As the title suggest I need to be able to showcase a react native app continuously during development every other day with a client which is not technical orientated. The alternativs I see is,
* Sharing a git/github repo for them to download and run through Xcode
which is not a possibility.
*Screen record while i run the simulation on my computer and share it
with the client
Both of these options seems subpar and not optimal.
How do I do this in a better way?
I am sorry if this seems like an open ended question and if you have suggestions on how to better formulate this question please provide it.
You can upload the binary to TestFlight, which allows your client to download and use the app instantly.
You can also consider over-the-air update systems like Expo or CodePush which allows you to deliver Javascript-only updates automatically to your clients when they open the app (just like a web app).
I'm building an in-house app that is distributed via the AirWatch app catalog. The app always runs with Guided Access enabled and all devices running it are managed by AirWatch. My questions are regarding auto-update:
Is there a way that AirWatch can force the update immediately or as soon as the device comes back online, without asking for the user's input? If so, how does the app being open affect this behavior? How does guided access being enabled affect this behavior?
Is there a link from AirWatch, perhaps an itms-services:// link, that the app can call to install the new version if a web service had indicated that it's no longer the latest version? If so, how does Guided Access being enabled affect this behavior?
Is there any other good model for remotely updating the app that will spread the update as quickly as possible and under the above conditions? The solution can be using MDM or a custom web service or both combined.
Thanks a lot for your help!!
If your devices are running iOS7 and you have your app Deployment settings set to "Auto" (as opposed to "On-Demand") the device will automatically take the update once it processes the APNs notification to do so. If the device is locked/offline it will typically check for outstanding APNs messages within a minute or so of being unlocked or coming back online.
What I don't know is since your app is in guided access mode if you're receiving a pop-up to install the new version. I've seen previously where if the app that requires an update is open iOS will prompt. What we have done to battle this is embed a check in the app that phones home to see if the app is current. If the app is NOT current the user can't do anything until they update their app.
Regarding a direct-link to the App Catalog to update the app that might get tricky with guided access enabled. Before you even try to tackle that issue understand that the app catalog webclip URL contains the UDID of the device as of AW7.1 (I think). Since the UDID is no longer programmatically accessible code-side AirWatch allows you to push the UDID upon app installation in the Deployment/Application Configuration section. You can embed {DeviceUid} into the key share on the device which will make it accessible for that applciation, hence allowing you to create the appropriate App Store URL within your app.
Good luck
honestly I didn't work with AirWatch. But I don't think that Apple provides a way for automatic update of ad-hoc or enterprise apps.
Well, I can describe a solution for an enterprise app I developed last year. Hope it will help you somehow.
First of all, I made it as a part of our secure website. (a little test flight)
Here's how app update works
When the app launches it sends special request to a server asking if
it is outdated and a new app version is available. (+ servers sends
url for new version installation (with itms-services://))
Then
if update is required, app fires alert with description of new
version, if user taps update, the app opens Safari where the user
is able to install a new version.
We made to different kinds of alert, optional (minor version change) and compulsory(major version change). With later variant user is unable to get rid of alert view, so he has to update the app.
You can update your internal app through the AirWatch Console and applications versioning.
I never used it but I imagine that at the end of the new version process, there is a way to push the updated app to the related devices. If the Push Mode is set to Auto, the user won't have to do anything and the app should be updated. If it is On Demand, the use will have to initiate the process from the App Catalog. From for the latest option, you have the solution to send a notification to the user.
It is also possible to retire or inactivate older versions to only keep the newest one.
If you have access to AirWatch Online Documentation, I recommend you the page Using Add Version for Applications. If you don't, contact your administrator and ask for all the pages located in Mobile Application Management -> Internal Applications and the page Using Add Version for Applications.
You should try it with a single device though ;)
We are ready to start the development of an using trigger.io, however some last minute external feedback pretends that trigger.io apps are systematically being rejected by Apple since the launch of their new Reload system (which pushes updated HTML/CSS/JS code without having to re-sublit to Apple for app updates).
The only reply regarding this topic on stackoverflow (Apple App Store ok with Trigger Reload?) was issued by one of the founders of Trigger.io, so I'm really looking for some totally independent feedback on this.
Can anyone provide any real-life feedback on this ? Has anyone ever succesfully submitted an app to the store ?
Trigger.io's page https://trigger.io/examples/ provides very few examples of submitted apps, so it isn't very convincing either...
Any feedback greatly appreciated !
At Hojoki, we're successfully submitting an app built on Trigger.io to the App Store for over a year now. We're actively using Reload (e.g. pushed reloads to all our iOS users three times in April) and never experienced any issues regarding approval and Reload.
There were two times that the app has been rejected (related to meta data stuff..), however this had nothing to do with Reload or Trigger.io at all.
The only Reload-related app store rejection we know of happened on May 9th (six days ago). This was due to Reload files not being marked as exempt from iCloud and iTunes backups.
There are loads of apps using Reload live in the app store, so it's not a general problem - it's just that this particular app was using Reload to distribute >100MB files.
Nevertheless, v1.4.46 of the Trigger.io platform contains a fix which sets the no-backup flag, to be extra safe.