Any SDK version is applicable.
I've tested from 3.5.0 to prerelease 3.7.0.
Whenever Building and testing my own worlds (doesn't matter which one) or even avatars according to others, it always seems to refuse to acknowledge the Blueprint ID as ours.
In my case I'd tried using both a clear world ID and a world ID that I've owned for several years and it seems like the SDK isn't the issue somehow.
Keep in mind that nothing in my project had changed and I had tested this on several different unrelated projects and they all came up the same.
----------------------------
This is the Error Code that typically has a
chance
to pop up after attempting a Build & Test or Upload of my world{s}:
[Always] Attempted to load the data for a world we do not own, clearing blueprint ID
UnityEngine.Debug:LogError (object,UnityEngine.Object)
VRC.Core.Logger:LogError (string,VRC.Core.DebugLevel,UnityEngine.Object)
VRC.SDK3.Editor.VRCSdkControlPanelWorldBuilder/<CreateContentInfoGUI>d85:MoveNext () (at ./Packages/com.vrchat.worlds/Editor/VRCSDK/SDK3/VRCSdkControlPanelWorldBuilder.cs:1199)
System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1<VRC.SDKBase.Editor.Api.VRCWorld>:SetException (System.Exception)
VRC.SDKBase.Editor.Api.VRCApi/<GetWorld>d23:MoveNext () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/API/VRCApi.cs:420)
System.Runtime.CompilerServices.AsyncTaskMethodBuilder1<VRC.SDKBase.Editor.Api.VRCWorld>:SetException (System.Exception)
VRC.SDKBase.Editor.Api.VRCApi/<Get>d__171<VRC.SDKBase.Editor.Api.VRCWorld>:MoveNext () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/API/VRCApi.cs:378)
System.Runtime.CompilerServices.AsyncTaskMethodBuilder1<VRC.SDKBase.Editor.Api.VRCWorld>:SetException (System.Exception)
VRC.SDKBase.Editor.Api.VRCApi/<MakeRequest>d__162<object, VRC.SDKBase.Editor.Api.VRCWorld>:MoveNext () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/API/VRCApi.cs:341)
System.Runtime.CompilerServices.AsyncTaskMethodBuilder1<System.ValueTuple2<VRC.SDKBase.Editor.Api.VRCWorld, System.Net.Http.HttpResponseMessage>>:SetException (System.Exception)
VRC.SDKBase.Editor.Api.VRCApi/<MakeRequestWithResponse>d__15`2<object, VRC.SDKBase.Editor.Api.VRCWorld>:MoveNext () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/API/VRCApi.cs:332)
UnityEngine.UnitySynchronizationContext:ExecuteTasks ()
----------------------------
I'd even checked the output logs and when It'd finally reached the point where it should've loaded the world it'd shown this:
2024.08.15 17:39:15 Log - [Behaviour] Connecting to realtime network
2024.08.15 17:39:15 Log - [Behaviour] Preparing assets...
2024.08.15 17:39:15 Log - [AssetBundleDownloadManager] Starting download of unknown MB, 0 still queued.
2024.08.15 17:39:15 Warning - [API] Attempted to authenticate non-API URI. No auth data was provided.
2024.08.15 17:39:15 Error - [Always] Error Downloading or Instantiating Custom Scene - Local Test - InvalidURL
2024.08.15 17:39:15 Error - [AssetBundleDownloadManager] Attempted to release an already released download handle.
2024.08.15 17:39:15 Error - [Behaviour] Downloading the room failed.
2024.08.15 17:39:15 Log - [Behaviour] World download took 16.3ms
2024.08.15 17:39:15 Log - [Behaviour] Resetting game flow because "Downloading the room failed": [ClearDestinationWorld, SkipLogin]
2024.08.15 17:39:15 Log - [Behaviour] waiting for UI Manager
2024.08.15 17:39:15 Log - [Behaviour] showing disconnect reason
----------------------------
The world only loads from 13-40 KB before kicking the player out and sending them to the error world when in testing mode, With said "Disconnect reason" being that I can't travel to online worlds in testing mode (presumably trying to kick me to the Default home world like online VRChat does when i try to load the incorrectly updated world).
This bug is something that I truly believe
cannot
be fixed on the user end and had suspiciously sprung up for many more creators only moments after VRChat had recently updated it's main branch for the new Hand IK release, among other things.
While this bug is unresolved there is seemingly no way for those affected by it to upload anything at all. While playing the game seems to be completely normal otherwise.