Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.4
2019.4
2020.3
2020.3.12f1
2021.1
2021.2
2022.1
Issue ID
1346797
Regression
No
Errors are not thrown when user declines to run API Updater for imported package with obsolete methods
Reproduction steps:
1. Create Unity 2019.4.x project
2. Import the attached package ("GoogleMobileAds-v6.0.1.unitypackage")
3. Click "Import"
4. Once the "Consent Request" window pops up, click "No"
5. If the "Consent Request" window would pop up again, repeat Step 4
Expected result: If user declines to run API Updater on an Imported package, that contains obsolete/removed methods, errors should be thrown
Actual result: Errors are not thrown when the user declines to run API Updater for a package with obsolete/removed methods
Reproducible with: 2018.4.36f1, 2019.4.29f1, 2020.3.14f1, 2021.1.15f1, 2021.2.0b5, 2022.1.0a3
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
- ShadowCaster2D does not update when using Sprite flipbook animation
- PropertyField with range attribute triggers change event when the value didn't change
- [Android] Soft keyboard is missing the "OK" button on Android
- The Profiler ignores a modified targetFrameRate when profiling Edit mode
- [General] Package manager takes 15 minutes to load
Resolution Note (2022.1.X):
Unfortunately there's not much we can do other than improving the message to make it clear that not allowing the ApiUpdater to run can lead to load/run time errors if there are assemblies that need to be updated (which we have done in 2021.x).
Unfortunately collecting the information to make the message more clear is a bit involved so we decided for closing the issue as "wont fix".
In case we get more requests/reports of similar issues, on versions 2020.x and older, we may reconsider improving the wording to be more clear on those versions.