Search Issue Tracker
Third Party Issue
Votes
0
Found in
2019.4
2020.3
2020.3.26f1
2021.2
Issue ID
1396566
Regression
No
[ironSource SDK] A unitypackage asset is imported after closing plugin's "Integration Manager"
How to reproduce:
1. Open the user's attached project "IronSourceImportBug.zip"
2. Navigate to Assets > IronSource > Editor in the Project window
3. Open the "ironSource Integration Manager" ("IronSource" > "Integration Manager")
4. Press the first "Update" button
5. Close the "ironSource Integration Manager" or open a different application
6. Observe the Project window
Expected result: No package asset gets created
Actual result: IronSource_IntegrationManager.unitypackage asset is created
Reproducible with: 2019.4.37f1, 2020.3.31f1, 2021.2.17f1
Could not test with: 2022.1.0b13, 2022.2.0a8 (InvalidOperationException: Insecure connection not allowed)
Add comment
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
Resolution Note:
Package Manager devs agree that the problem would be in the 'Integration Manager' from the IronSource SDK and not Package Manager. There is no file getting 'imported' in the project here, the 'Integration Manager' seems to be the culprit by creating this file.