Search Issue Tracker
Fixed in 1.0.4-preview.6
Votes
0
Found in [Package]
2018.4
2018.4.12f1
2019.2
2019.3
2020.1
Issue ID
1198043
Regression
Yes
Unity.Mobile.Notifcations.Editor.asmdef is not auto-referenced and cannot be referenced from another script
How to reproduce:
1. Open user-submitted project (NotifyMe)
2. See that the Editor script 'Scripty.cs' compiles successfully
3. Remove the 'Scripty.asmdef' asset from the Editor folder
Expected result: Scripty.cs compiles successfully
Actual result: Scripty.cs fails to compile due to UnityNotificationsSetitngs not existing in current context
Reproducible with: 2018.4.13f1, 2019.2.13f1, 2019.3.0b11, 2020.1.0a13
Could not test with: 2017.4.34f1(Mobile Notifications package unavailable)
Reproducible with package versions: preview.10 - 1.0.0, preview.4 - 1.0.4
Not reproducible with package versions: preview.9 - 1.0.0
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Add comment