Questions

Greetings, I've downloaded the latest "Rebuilt source code" for our app (Android version) to debug something locally and I've discovered that trying to compile it I receive the following Gradle error when trying to run it in debug mode (any mode actually): **_Could not GET '<https://jitpack.io/com/github/gonativeio/gonative-icons/1.3.0/gonative-icons-1.3.0.pom'>. Received status code 401 from server: Unauthorized_** As far as I can see, it tries to download this dependency from jitpack, maven and dl.google.com, only being available in jitpack at the given URL, but accessing it requires authentication, which we don't currently have access to (nor configured anywhere within the app). Is there something we're missing / wrongly configured within the dashboard, or should that package be publicly available and it's a temporary issue? I didn't go further removing that dependency as I'm not sure if removing it causes other issues, so I'd better ask first. <br /> <br /> Thanks.

Hello, Please, I made applications using a tool from a company that develops applications, and now I have this problem below. **\*\*** We detected that your app is intended for an old version of Android. To provide a secure experience for users, Google Play requires that all apps meet the desired API level requirements. Starting August 31, 2024, if your desired API level is less than one year different from the latest version of Android, you won't be able to update your app. ****\***** Today I met Median and created AAB to redo the applications. I would like to know if I will not have this same problem, as I marked ADVERTISING ID within the play console content and was asked to disable Android 13 launch errors. (I understood the consequences of not including the com.google.android permission. gms.permission.AD_ID in manifest file when targeting Android 13 and want to disable version errors) I would like to know if I will have the same problem with an outdated Android version if I launch AAB for closed test analysis. I used free Median to generate the apk and aab. Thanks

Dear Median team. We get refuse by Apple and here is their reply: Your app provides a limited user experience as it is not sufficiently different from a web browsing experience. As such, the experience it provides is similar to the general experience of using a web browser. Including features such as push notifications, Core Location, or sharing do not provide a robust enough experience to be appropriate for the App Store. Can you give me some suggestion? Thank you very much

After rebuilding my apps to meet the request for API 34, they no longer ask for location permissions on startup. Why is that?

If I start with the free tier app, but decide to upgrade later… Can I push an update to the app? How do updates work?

Hello, <br /> I have part of my app build as a static HTML page and tring to open it with a AppBrowser. Following is the setting I have in Link handling. ```json json { "active": true, "rules": [ { "mode": "external", "label": "Non-web links", "pagesToTrigger": "custom", "regex": "^(?!https?://).*" }, { "mode": "appbrowser", "label": "Contents pages", "pagesToTrigger": "custom", "regex": "https?:\\/\\/([-\\w]+\\.)*example.com\\/contents(\\/.*)?$", "custom": true }, { "mode": "internal", "label": "All pages on my domain", "regex": "https?:\\/\\/([-\\w]+\\.)*example.com(\\/.*)?$", "custom": true, "pagesToTrigger": "custom", "url": "https://" }, { "mode": "external", "label": "All Other Links", "pagesToTrigger": "all", "regex": ".*" } ] } ``` When <https://example.com/contents/anything.html> is opened with any method (window.open, location.href, router.push ... ) the app hangs up. I also tried opening /contents/anything.html, but the result was same. This happens only on android and the redirect rule was set to "appbrowser" and the domain is same as the origin. (i.e. ios or internal or other domain like <https://example.net/index.html> works fine.) Cloud you take a look on this?

Hi, I rebuilt my Android AAB files yesterday due to this message in the Play Store, but I'm still getting a message from Google that yesterday's build is still targeting older versions of Android. Why are new builds still having this issue? I have a valid and active App updates plan subscription.

Hello Team, its been a bit frustruating getting share to plugin to work as we expect. Our main website runs next js 14. We are able to get the url information in our app but the callback gets triggered randomly. Everytime we navigate to in our application, the callback get triggered and runs. The information in the share to never gets dumped after the callback runs. Any solutions?

Hello, I received a message from Google saying that i need to update my published app on Google play store to meet target API level requirements. Android 14 (API level 34) precisely. After rebuilding my application and republishing the new AAB File, in the google console the API level is still 23 or earlier as the previous AAB. He hasn't upgraded to level 34. how to fix this problem please? THX

Package '${applicationId}.test' from AndroidManifest.xml is not a valid Java package name as '${applicationId}' is not a valid Java identifier. <br /> I get this error, when I build with downloaded source code in the android studio. Did not change any setting but to just upgrade android sdk version. Please give any advise on this. <br /> Thank you.