Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.6.0-pre.3
Issue ID
UVSB-1529
Regression
No
[Bolt][Android] Multiple connection warnings appear relating to Graphs when building for Android after upgrading to 2021.1
Reproduction steps:
1. Open the project located on https://drive.google.com/drive/folders/1yC77Yv3knd6SwQ_a4tiB7KxVYwKb1IdL?usp=sharing
2. Build for Android with Autoconnected Profiler turned on
3. Observe in the Console Window multiple warnings "Autoconnected Player Could not load connection between 'result' of 'InvokeMember#07ba3...' and 'target' of 'SetMember#f11cd...'."
Expected result: multiple connection warnings do not appear relating to Graphs when building for Android after upgrading to 2021.1
Actual result: multiple connection warnings appear relating to Graphs when building for Android after upgrading to 2021.1
Reproduces on: Bolt 1.6.0-pre.3 - Bolt 1.6.1 (2021.1.9f1, 2021.2.0a18)
Could not test on 2019.4.27f1 and 2020.3.10f1 due to how the issue manifests
Could not test on 2018.4.35f1 due to the project breaking when downgrading
*Notes:*
- An android device must be connected. After talking to CQA they pointed this out as it is not described on the ticket
{code:java}
when a device is connected and the APK is built to a device then the warnings appear.
{code}
- The issue manifested after upgrading from 2019.4 to 2021.1
- Workaround is to rebuild the graphs that exhibit the warnings
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
- A 404 page is opened when selecting "Open Documentation" on the Float Node in Shader Graph
- Shader Graph Importer's Documentation Reference button leads to a 404 page
- Crash on WriteParticleLineVertex when particle systems are rendered in a specific project
- Asset names longer than the allowed system file path are not handled gracefully
- Moving VFX Particles leave a ghosting trial in Ray Traced Screen Space Reflections
Resolution Note:
We won't fix this issue for VS 1.6 since that version is about to be deprecated. However, we have tested the issue using VS 1.7.5 Editor 2021.2.2f1 and we were not able to reproduce it. If the user complains again about this after updating the Editor + VS version, please feel free to contact us back and we will reopen this bug.
Please refer to the comments to see the developers note.