Search Issue Tracker
Not Reproducible
Votes
2
Found in
Issue ID
1004883
Regression
No
[FixInGit1.4] Unable to publish projects with Unity IAP enabled/imported
ISSUE:
If the user enables IAP for a collaborate-enabled project and then tries to publish, they receive a "MD5 does not match" error and cannot publish.
WORKAROUND:
Restart Unity after importing IAP when using Collab. You should then be able to publish to Collab without issues.
REPRO STEPS:
1. Create a new project in any Unity Editor.
2. Enable Collab and make a first commit/publish.
3. In the service window, enable Unity IAP, then import all of the IAP assets, then select "go ahead" to update obsolete APIs
4. Attempt to publish your project after the IAP assets are successfully imported
RESULTS:
User receives a "MD5 does not match" error and cannot publish
EXPECTED:
User can publish normally
Reproduced in 2017.1.0f3, 2017.3.0p4, 2018.2.0a2 (Trunk)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment