Removing a Specific Child Object in a Content Update Causes an Error.

Open

#77 opened on May 24, 2022 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: android, csharp, google-cloud, unity
Domain: cloud, game-dev, mobile-dev

Research direction

Start by following the listed Addressables reproduction steps in the Unity project, using the Unity-chan FBX child replacement and remote content hosted in Google Cloud Storage. Inspect the Android logcat error and the linked Unity Forum details; done means the updated prefab loads in the Addressable scene after the content update.

Written by the indexing model from the issue text.

Description

I posted this on the Unity Forums https://forum.unity.com/threads/unusual-behaviour-removing-a-specific-child-object-in-a-content-update-causes-an-error.1285517/ but I decided to put this as an issue for people to notice here.

The details are in the link above. To summarize the context and the problem:
Context: Using Addressables with remote content delivery via Google Cloud Storage (Bucket created using Firebase) and testing it with Unity-chan package fbx models.
Steps:

Create a prefab with the "unitychan" 3D fbx model as a child object.
Build content, upload content into cloud, build player, and play on Android to see it all work fine.
Update the prefab by changing the child object "unitychan" 3D fbx model into something else. A sphere, cube, or whatever.
Update existing build and upload it to cloud.
Play on Android.

Expected result: prefab is updated with whatever was replaced.
What happens: Addressable scene does not even load and this error appears in the Android logcat:

Dominant language: C#
Stars: 1.5k
Forks: 303
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.