Posts

Post not yet marked as solved
5 Replies
5.3k Views
My company has submitted 2 apps to the iOS store. One is for a "Producer" and the other is for a "Driver".Producers will request a pickup of a commodity. This request is assigned to a Driver and the Driver will follow directions to get to the Producer, pickup the load, and then transport the item to the destination.The Producer App gives the Producer visability of where the Driver is. We also have a web app that allows us to see wheree the Drivers are.The Producer App was approved and is in the App sgtore.The Driver App has been rejected:Guideline 2.5.4 - Performance - Software RequirementsWe noticed that your app declares support for location in the UIBackgroundModes key in your Info.plist file but does not have any features that require persistent location. Specifically, your app uses location background mode for the sole purpose of tracking employees, which is not appropriate on the App Store.Next StepsTo resolve this issue, please revise your app to include additional features for your users that require the persistent use of real-time location updates while the app is in the background.The app DOES have other features: Drivers can submitt invoices direcectly from the app, and can then get paid sooner. The Drivers are not our employees, they work for themselves. They don't have to use the app. We do ask for permissions. We have appealed and added information concerning the other features of the app, but we are rejected every time. I am kind of at a loss as to what we can do.All of our apps are built in Xamarin, if that is of any help.Any suggestions would be greatly appreciated.Bryan
Posted Last updated
.
Post not yet marked as solved
0 Replies
280 Views
I am confused about how to add a trusted phone number and trusted device to my company's main Apple Account, the one who is the Account Holder. I understand that we need to: Obtain an iOS device that is associated with a phone line. Create an Apple ID that is controlled by my company. Add the Apple ID to the device. Set up 2 factor authentication. Sign into https://appleid.apple.com/account/manage#!&page=signin with the new ID and select Account Security. Then select to add a new Trusted Number. Enter the phone number assigned to this new device and continue. Now we have a backup account and device that can be used to access the account if the Account Holder or the device associated with the Account Holder is not available. Is this correct? Do we have to have a device that has a phone number? Someone suggested that you could use an iPod Touch as a second device, but you cannot assign a phone number to an iPod Touch, right? I am very very interested in following best practices with regard to this and would appreciate any information or links to information on best practices.
Posted Last updated
.
Post marked as solved
3 Replies
958 Views
I just got the following from Apple:Dear Developer,We identified one or more issues with a recent delivery for your app, Please correct the following issues, then upload again.ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview).Best regards,The App Store TeamI understand that this is deprecated for new apps in 4/2020 and for updated apps in 12/2020. This is NOT a new app.We have got this message many times before. New apps have to have this completed by April 2020, Updated Apps by December 2020.To us this is an updated App. It has been in Test Flight for over a year and we updated date it about every month. We use a different a unique app bundle for promotion to the App Store. I don't know why.The only thing I can see that we did differently was we needed a new provisioning profile. But that shouldn't mean it is a "new" app.What criteria does Apple use to indicate whether an app is "new" or "updated".
Posted Last updated
.
Post not yet marked as solved
0 Replies
469 Views
I am experiencing a strange, reproducible bug in Test Flight while trying to update an application. We are using release version of iOS 13.3. The device in question (one of the devices anyway is a 3 week old iPhone 11 Pro Plus. I assign user to version x in TF, download app, sign in. App is in foregroundI assign user to version x + 1 in TF, TF shows Update, I upate. Progress wheel spins toward end and stops.I return to the app and can to things normally.App does not update.If I kill the app (and sometimes also kill Test Flight and relaunch), then the update will update. I do not open the app. The app has the normal updating greyed out look, cannot get into the app, all is well.We can reproduce on other devices.Does anyone else have this problem? Can I use Xcode to see what is happening.
Posted Last updated
.
Post not yet marked as solved
1 Replies
430 Views
We have used Test Flight to test two apps that work together. In June we released the both apps to production; one app was accepted and one was rejected. We went ahead and continued to use the test version of the rejected app while we considered how to change the app to get approved or appeal.We have appealed and are waiting to hear back from Apple. Understand it is important to be patient.We have some features that we need to release for this fall (our apps are seasonal) which we would like to release in about a week or two. I am concerned that Apple may not reply to use before we need to release some changes for testing, but we don't want to mess up the appeal we have already outstanding.Can we put another build in Test Flight with the same bundle ID but increment the version number from 1.0.x to 1.0.x+1? I fear that will interfere with our appeal, or possibly annoy Apple, which we don't want to do. Is it better to change the bundle ID if we cannot get our appeal resolved before we have to get another test version out? What is the best way to approach this issue?Thank you very much.
Posted Last updated
.