Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3.6f1
2019.4
2021.1
Issue ID
1229959
Regression
No
Collaboration lose Unity Team access when macbook's lid is closed and reopened
How to reproduce:
1. Create a new project
2. Open the Collaborate window and press the 'Set Project ID' button
3. In the Project Settings window, set organization
4. Press the 'Set Project ID' button in Project Settings
5. Enable Collaborate in Project Settings
6. Create a few Materials in Project Browser
7. Close the laptop's lid and wait for about 10 secs
8. Open the lid
9. Publish changes
Expected result: Changes are saved with no errors
Actual result: 'Refresh complete. Access required for Unity Teams', 'Requires Unity Teams' errors are thrown, or stucks on 'Committing changes to server' message. Changes can not be published until the Editor is restarted
Reproducible with: 2019.4.14f1, 2020.1.10f1, 2020.2.0b10, 2021.1.0a4
Can not test with: 2018.4.29f1 when publishing changes nothing happens
Notes:
- Tested using MacBook Pro (macOS 11.0 Beta)
- Video of reproduction is attached in Edit
- Not reproducible with Lock Screen or Sleep methods, closing the laptop's lid is necessary
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
- Editor UI Text is displayed incorrectly or blank, and "Unable to load font face for [System Normal]." and other warnings are spammed when Editor Font is set to System Font and TMP Package is imported
- TabView with icons is smaller in height then other tabs with text
- [iOS] Error shows and "Microphone.GetPosition" logged as zero when "Microphone.Start()" is called the first time while a microphone is busy in another app and the second time when the microphone is released
- Inconsistent Layout in Project Settings Panels
- "Check for Updates" Fails to Connect to Update Server
Resolution Note (2021.1.X):
Collab is currently transitioning into maintenance mode as the team works on a replacement offering, which will be announced in the coming months. Closing this bug as Won't Fix.