User Profile

Greetings all,The dev company that I work for has been contracted to build an app for a small client with 100 employees. This client is using Apple Business Manager and wants us to publish our app to it.I have built the app and deployed it for review to Apple Connect. It successfully passed the review process, and I see it is now in the client's Apple Business Manager account as a Custom App.What to do next? Here is where I am confused. Our client DOES NOT have a MDM. How can I use Apple Business Manager in this case? From the apple site (https://developer.apple.com/business/custom-apps/), it says "Alternatively, organizations can choose to provide redemption codes to authorized users to download the app on the App Store.".My understanding is that redemption codes are like "gift cards". Once they are used, there is no way to call them back. This is not going to work for the client as they employ many field workers and short term contractors, and need to be able to revoke the app once the contractor leaves.My understanding is I need to use the Managed License section of ABM. I have read, and read, and read, and everything seems to indicate that a MDM is mandatory in this case. The following 3 links from Apple make this clear:https://support.apple.com/en-ca/guide/mdm/mdm55049a109/webhttps://support.apple.com/en-ca/guide/deployment-reference-macos/apdb421c7f34/1/web/1https://support.apple.com/en-ca/guide/apple-business-manager/asm6a88f692e/1/web/1I am really struggling here folks to help our client. Surely, there must be something that can be done. The client simply want to distribute the app to all its employees, contractors, and business affiliates. They have simple goals. Nothing fancy. They simply want to be able to know who has the app, and therefore be able to revoke the license at any time if a employee with the app leaves/terminated, or has thier contract end.Please help!Derek

Hi there,Our dev team is continually getting these strong warning messages whenever we submit an app to the Appstore.ITMS-90809: Deprecated API Usage - Apple will no longer accept submissions of new apps that use UIWebView as of April 30, 2020 and app updates that use UIWebView as of December 2020. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview).This concerns me as we are almost at the end of the April. I'd like to know the extent of this.What is the difference between 'new apps' and 'app updates'. My understanding is that NEW APPS means new apps that are submitted to the ap store with a new bundle idm ew SKU, and new Apple ID. This flow will not accept submissions of new apps that use UIWebView as of April 30, 2020."App updates" assume that an app already exists in the app store (with a Bundle ID, SKU, Apple ID), and so updates (new builds to this app) wil be allowed up the December 2020.Please clarify.

Hi there, I have an app in the Appstore that is 3.4 build 0.0.2 (Ready for Sale), but I found a small bug that I need too push out. It seems silly to update the version to 3.5 just for this small bug that we missed in testing. Is there anyway that I can remove the 3.4 from sale and simply create a 3.4 0.0.3 (three) and submit this for review. Is this possible?

Hello, I have 3 unused App Identifiers that I want to delete from my developer account. However, when I attempt to delete them, I get an error that they cannot be deleted as they are in use by the Appstore. However, I can 100% guarantee that these are not in use. Why can't I delete them? The error message reads: There is a problem with the request entity The App ID <removed for security> appears to be in use by the App Store, so it can not be removed at this time.

Hello,I have 2 questions. We have an app is in the Apple store.Details:Name: BGGoPlan Lite EditionBundle ID: abm.bggoplan.app.liteSKU: bggoplan.app.liteApple ID: 1506618740Question #1:- I have 3 iOS App Store Versions. Version 4.0, Version 3.4, and Version 3.3. All three are listed as "Ready for Sale". Version 3.4 (YES 3.4) is the current version that people are downloading (good). However, I want to clean things up as it is confusing for our admin team.Q. How do I delete Version 4.0 and Verison 3.3 (NOT builds) from the App store.Question #2:- Similar to above, for iOS Builds, I have Version 3.4 (build 0.0.5, build 0.0.4), Version 3.3 (build 0.0.3) and Version 3.2 (build 0.0.2). Version 3.5 (build 0.0.5) is the latest one that people are presently downloading. How can I delete iOS builds Version 3.3 (all incl' builds), and Version 3.4 (all incl' builds)?I have uploaded screenshot of the above into my Google drive at the link below:https://drive.google.com/open?id=1SPVJ_xGmelXayZsoyNjmg4TAP6892cyDPlease advise how I can do this cleanup task?Derek

Hi there,I apologize if this question has been asked already, but I was not able to find an answer though this forum or Stack Overflow.I am a relative new user to Apple Connects, bear with me.I have presently have two iOS Builds of our app in Apple Connect (3.3, 3.4). The latest one is 3.4 is listed as "Ready for Sale"Question:1) How can I revert back to an previous iOS Buld (say 3.3) and make this build version "Ready for Sale"?2) I have an older iOS App Store Version that I wish to delete. How can I do this?Derek

I understand that it is now possible for an organization to provide B2B apps to themselves. The advantage of B2B apps is that they never expire and don't require periodic provisioning profile validation and refresh.I am unclear on how this is possible though? Apps are build (using Xcode) such that they require a provisioning profile to be built. If this profiles expires, the app can no longer be launched. So how does B2B make apps never expire.My understanding is the flow is as follows:1. Build the app using code. Requires both a distribution profile, and a provisioning profile for the archive build to complete.2. Publish the app to Apple Connect and mark it as a B2B custom app (using the a DEP id).3. Once the app passes (we assume success) the review process, it shows up as a custom app in Apple Business Manager land.4. I can deploy the app via VPP Codes that I issue to users, or as a managed license.This is where I am confused. Let say I do nothing for the next 2 years. The provisioning profile that the app was originally built with has now expired. So how is the above statement correct? "The advantage of B2B apps is that they never expire and don't require periodic provisioning profile validation and refresh"?*** Update:*** I did some further research, and I'd like some extra clarification. My understanding is that when it comes to BOTH Enterprise and with Custom apps, in both cases, I need a valid distribution profile, and a valid provisioning profile for the archive build to complete, this is where the similarity ends.In the Enterprise program (which I am most familiar with), I would have to police the app, and make sure that the provisioning profile used to build the app, doesn't expire. This extra precaution is necessary because by going the Enterprise route we are bypassing the Apple Connect review process ... essentially taking responsibility into our own hands. Hence the need for us to be cognizant of the provisions profile expiry dates.However, we have MUCH more flexibility under the Apple Connect route. Since the app is being formally reviewed and distributed as a B2B custom app, the app is re-signed in Apple Connect/Apple Business Manager (ABM) when then provisioning profile is near expiry; so the provisioning profile then never expires.So returning to my example. Let say I do nothing for the next 2 years. The provisioning profile that the app was originally built with has now expired in developer.apple.com. It is of no concern of mine, as the app it was built with has been re-signed by apple (and hence can continue to be purchased via ABM.)But.. if I plan to build a new version of the app using that same (now expired provisioning profile in developer.apple.com), I will have to first **** away and recreate the provisioining profile (in developer.apple.com)Is my understanding correct?

The small dev company that I work for has been contracted to build an app for client. This client is using Apple Business Manager and wants us to publish to it.I have built the app and deployed it for review to the Apple Connect. It passed and I see it is now in the client's Apple Business Manager account.Here is where I am confused. Our client DOES NOT have a MDM. How can I use Apple Business Manager in this case?Initially I thought I could simply use redemption codes, but now I see that this is not going to work, as redemption codes are similar to "gift cards" that we give out to people. Unless I am mistaken, there is no way to manage them and revoke them when we need so.It seems that the only way to manage the licenses is to implement a MDM (like Mobile Iron, etc.), but this seems like a lot of work. There must be another way. What about contractors that require a corporate app? Surely, there has to be a way to use the Managed Licensing aspect of ABM without using a MDM.How can use ABM to do "managed licensing" without our client(s) having a MDM. Is there a way that I can revoke a redemption code once I have issued it?