need to wrap android bundle without converting it into apk

[sagamagus]

Describe the bug: With the new policy of google playstore we cant upload apks anymore, we need to upload aap bundles, thats the reason because now we need the wrapping tool to let us wrap android app bundles .aap files

[rygo-msft]

Hi @sagamagus,

So that we understand your scenario, are you publishing your app as a public Google Play Store listing, or is this a private listing? There was a known issue in the Google Play Developer console where apks were being blocked for private uploads. My understanding is that issue has been resolved and the ability to upload private listing apks should no longer be blocked.

[zalaris]

Hi @rygo-msft ,

Our scenario is quite the same. We are uploading the app to public Google Play store listing. New Google Play policy allows only .aab (App Bundle) binaries to be uploaded. So we need the wrapping tool to support .aab binaries.

[meghandaly]

Hello @sagamagus and @zalaris, the new Google policy applies to apps published to the public Google Play Store. As @rygo-msft mentioned above, it does not apply when publishing private apps. While there was an issue where APKs were blocked that has been remediated.

If you are indeed publishing your apps to the public Google Play Store, that is unexpected given all wrapped apps require policy to be applied. We are working on the App Wrapper supported AABs in the future, but we do not have a timeline available.

In the meantime, the following may be avenues to explore to unblock updates to your app.

If your app allows non-policy managed users, you should be integrating the SDK with the Gradle Build Plugin. A wrapped app is only expected to be used in LOB scenarios where all users are managed by policy.

If your app only allows policy managed users, you should be publishing and distributing the app privately, as most customers deploying LOB apps do.

[mikektmobile]

@meghandaly is this still only a Feature request. We have an intune wrapped app for the public app store for ios, its a multi tenant app just like slack, teams, webex. We want to do the same for Android, and need a .aab file. This is not private, as well need customers to be able to find it just like Apple

[fangornoftheforest]

Hello @sagamagus and @zalaris, the new Google policy applies to apps published to the public Google Play Store. As @rygo-msft mentioned above, it does not apply when publishing private apps. While there was an issue where APKs were blocked that has been remediated.

If you are indeed publishing your apps to the public Google Play Store, that is unexpected given all wrapped apps require policy to be applied. We are working on the App Wrapper supported AABs in the future, but we do not have a timeline available.

In the meantime, the following may be avenues to explore to unblock updates to your app.

If your app allows non-policy managed users, you should be integrating the SDK with the Gradle Build Plugin. A wrapped app is only expected to be used in LOB scenarios where all users are managed by policy.

If your app only allows policy managed users, you should be publishing and distributing the app privately, as most customers deploying LOB apps do.

Hi @meghandaly, unexpected may be true, but it seems like it's definitely happens. We offer a SaaS product where each customer has their own server and they use their own Azure tenant to connect to this SaaS environment. Our app can connect to this server using OIDC. However, this method of authentication is blocked when the company uses Intune to manage their employees' devices as it is not an allowed app. Our app only needs to be compatible with Intune, so it can be added as an approved app, so users can actually log-in.

The wrapper tool only working for .apk's is a real blocker.