Arshan Khanifar

+1 having the same issue here.

I realized my problem was that I was actually building a `bundle` instead of an `APK`. So I changed my `releaseDirectory` to: `releaseDirectory: android/app/build/outputs/apk/release` and also invoked `./gradlew` with `assembleRelease`....

@mindaugasnakrosis Sorry I don't know about app bundles just yet so don't have anything to add to ur stackoverflow question for now. I remember when I was making the key,...

@mroczis If it's okay with you to share, which logs exactly does Netmoster look at to make a guess about the secondary cells?

thank you @SerCeMan for the timely response, should I close this then?

ah I noticed #825 's similar to this.

anybody working on this? would be a killer feature to have.

I have some private `bundledDependencies` that yarn attempts to install from npm package registry even though I've added the `resolutions` field :( ``` "bundledDependencies": [ "@decent.xyz/box-common", "@decent.xyz/box-hooks", "@decent.xyz/box-ui", "@decent.xyz/box-evm" ],...

I fixed this by publishing empty packages to npm with the same name as my private packages. For some reason yarn wants to ensure those packages exist on the registry...

Already had a jab at it following [this blogpost](https://quickbirdstudios.com/blog/swift-package-manager-cocoapods-support/) on [a fork I made](https://github.com/ArshanKhanifar/mlx-swift), but had no luck when installing from cocoapods: ``` pod 'mlx-swift', :git => 'https://github.com/ArshanKhanifar/mlx-swift.git', :branch =>...