When publishing an app using Application Publisher, after nearly ten minutes, I get the following error...
The status is FAILED for the file named
/var/folders/yt/v3w7j1ws45d7s_7328dyn_6c0000gn/T/e6e327f5-e6b6-4645-876e-042274753a135949007606868121680dir/64fb63f5-da16-43cd-9b01-4f4ce22e23536929388045350435111.txt
and the error description is 'Destination: Disk quota exceeded (5)'
Any ideas?
Looks like apple might be having some server issues, though their status page says otherwise, I too am getting this issue
https://developer.apple.com/system-status/
I had the exact same error. My problem was that I was trying to upload an archive with the same version number as already reviewed and published on the app store. The solution here was to:
login into app connect, select the app
create new version app version: "(+) version or platform"-button in the left menu
set new version number
distribute new archive with exact same version number as set in app connect
Upload is now successul
Related
Currently, my Unity Android app that I uploaded as a production on Google Play has a big problem.
We started Google As advertisement and checked the inflow of users (installation of 1,597),
However, there are only 67 users who have actually accessed it...
I downloaded my app that I uploaded to Google Play directly and logged in with my Google account, so there was no problem, and I asked my friend to download and run the app, so there was no problem logging in.
The predictable problem is that due to the number of concurrent users, many users are unable to access when starting the advertisement, or something seems to be wrong with my GPGS setting.
Please check the possible problems and the image of my GPGS setup.
**Setting **
Unity Ver : 2021.3.8f1
GPGS Plugin : 0.10.14
State
Upload Google Console Production
Google Console -> Play Games Services -> Setup And Management -> Configuration -> Publish Complete
Create 3 Google Cloud Platform OAuth Clients
-> Upload key, app signature key, server
1. Suspected Problem 1
If the AndroidManifest.xml Package Name is different from the package name of the Google Console, can the Production user not access it?
Unity -> PlaySetting -> Identification -> Package Name is entered as the package name of the Google Console, but AndroidManifest.xml Package Name is marked as package="com.google.example.games.mainlibproj" and modified it directly to the package name of the Google Console, but it was restored again.
enter image description here
enter image description here
(If it is a problem and you need to check the Unity error list, you can attach it later)
2. Suspected Problem 2
Can't the user access because Unity's keystore certificate is set to upload authentication signature, not app authentication signature?
enter image description here
3. If you have any other problems, please give us your opinion.
There was an error uploading the Android App Bundle. Try again later or contact Google Play developer support if the error persists
I am getting this error and I tried resolving it using multiple things like clearing cookies, using different browser, using different internet connection. Nothing Worked.
Any help will be appreciated.
Thanks
That can happen if the app bundle you're trying to upload has the same version code as an app bundle that has been already uploaded. Double check to see that it has a higher version code.
I'm using the standard environment of app engine.
I've deployed my app many times in the past, but today, although I've deployed new features App Engine, it serves an old version.
I've deleted all the versions and redeployed the app.
Verified in consol that the source files are the correct ones.
When deploy the (only) default version by its id I see the updated app (gcloud app browse -v VESION_ID), but when I load the app regularly (gcloud app browse) I get an old version that not exists anymore.
If I hard-reload (ctrl+shift+F5) I get another old version (different from the one it serve by default) but when I reload the page again (ctrl+F5) the other old version come back.
Any help would be appreciated to make App engine serve the most updated version.
One of the information at https://developer.chrome.com/webstore/get_started_simple states that “5. After you publish your app, whenever you want to change your app's listing or .crx file, use the dashboard to update them. To push an updated .crx file for your app, just increment the version number in the manifest, upload a new ZIP file to the dashboard, and publish the change. People who have already installed your app will automatically get the update.”
As per that, whenever, for a given app, an updated CRX file (i.e., new version of app) is uploaded in the webstore, the client devices where the older version of app was previously installed would get updated (with the new version of app) automatically.
However, I’ve requirement, where the new version of the app shouldn’t get updated automatically - even if the new version of the app is uploaded in the 'webstore'.
Is there a way to accomplish that?
We've been getting this installation error when our users try to install the apps marketplace app.
How do we resolve this?
Is the error being seen by Google Apps domain administrators or non-admin domain users? If its latter then its likely the domain administrator has not enabled install for non-admin users in the domain.
I've figured out the issue but do not know how to resolve this.
We had tried to update our marketplace app manifest file but due to some issue on Google's end, the updated manifest file was not being uploaded and this error was being thrown
This item is not an app, please remove app section from manifest , google apps marketplace
So we removed the "app" section from the manifest file and uploaded it. This has resulted in our marketplace app becoming a Chrome extension rather than a marketplace app and causing the issue.
Currently if I try to edit and upload a version of manifest file with "app" section, it won't allow me to upload it, showing the same error as before. So there is no way that I know which can solve this issue.
If anyone can help me out with this it will be really helpful. Registering a new MP app, getting approval from google and moving all users and reviews to new app will be really painful.