Post

Replies

Boosts

Views

Activity

Reality Composer Pro Assistant: "Authorization failed" when adding custom Azure AI Foundry OpenAI provider
Hello everyone, I am trying to configure a custom model provider inside the new Reality Composer Pro Assistant settings panel using an LLM hosted via Azure AI Foundry. Despite verifying my credentials and testing multiple base URL structures, I am persistently encountering the following error: Authorization failed — check your API key My Configuration Details: Target Model Deployment: gpt-5.1-codex-mini (GlobalStandard deployment type) Azure AI Foundry Endpoint Pattern: https://azure.com API Key Header Used: api-key What I Have Tried: Utilizing the Azure OpenAI format: https://<project-name>.services.ai.azure.com/openai/v1/responses Verifying the API key explicitly with headers like api-key and Authorization (testing both raw keys and Bearer <key> prefixes). It appears that Reality Composer Pro's validation step might be calling a standard GET /v1/models route or structurally modifying the outbound request in a way that causes Azure's gateway architecture to reject it with a 401 response code. Has anyone successfully mapped an Azure AI Foundry endpoint directly to the Assistant interface? If so, what is the exact base URL syntax and header structure expected by the desktop client to pass authorization? Thanks in advance for any insights!
0
0
438
1w
Alternatives to SceneView
Hey there, since SceneView has been marked as „deprecated“ for SwiftUI, I‘m wondering which alternatives should be considered for the following situation: I have a SwiftUI app (for iOS and iPadOS) where users can view (with rotate, scale, move gestures) 3D models (USDZ) in a scene. The models will be downloaded from web backend and called via local URL paths. What I tested: I‘ve tried ARView in .nonAR mode, RealityView, however I didn‘t get the expected response -> User can rotate, scale the 3D models in a virtual space. ARView in nonAR mode still shows the object like in normal AR mode without camera stream. I tried to add Gestures to the RealityView on iOS - loading USDZ 3D models worked but the gestures didn’t). Model3D is only available for visionOS (that would be amazing to have it for iOS) I also checked QuickLook Preview however it works pretty strange via Filepicker etc, which is not the way how the user should load the 3D models in my app. Maybe I missed something, I couldn’t find anything which can help me. I‘m pretty much stucked adopting the latest and greatest frameworks/APIs in my App and taking the next steps porting my app to visionOS. Long story short 😃: Does someone have an idea what is the alternative to SceneView for USDZ 3D models? I appreciate your support!! Thanks in advance!
4
0
713
Jul ’25
Reality Composer Pro Assistant: "Authorization failed" when adding custom Azure AI Foundry OpenAI provider
Hello everyone, I am trying to configure a custom model provider inside the new Reality Composer Pro Assistant settings panel using an LLM hosted via Azure AI Foundry. Despite verifying my credentials and testing multiple base URL structures, I am persistently encountering the following error: Authorization failed — check your API key My Configuration Details: Target Model Deployment: gpt-5.1-codex-mini (GlobalStandard deployment type) Azure AI Foundry Endpoint Pattern: https://azure.com API Key Header Used: api-key What I Have Tried: Utilizing the Azure OpenAI format: https://<project-name>.services.ai.azure.com/openai/v1/responses Verifying the API key explicitly with headers like api-key and Authorization (testing both raw keys and Bearer <key> prefixes). It appears that Reality Composer Pro's validation step might be calling a standard GET /v1/models route or structurally modifying the outbound request in a way that causes Azure's gateway architecture to reject it with a 401 response code. Has anyone successfully mapped an Azure AI Foundry endpoint directly to the Assistant interface? If so, what is the exact base URL syntax and header structure expected by the desktop client to pass authorization? Thanks in advance for any insights!
Replies
0
Boosts
0
Views
438
Activity
1w
Alternatives to SceneView
Hey there, since SceneView has been marked as „deprecated“ for SwiftUI, I‘m wondering which alternatives should be considered for the following situation: I have a SwiftUI app (for iOS and iPadOS) where users can view (with rotate, scale, move gestures) 3D models (USDZ) in a scene. The models will be downloaded from web backend and called via local URL paths. What I tested: I‘ve tried ARView in .nonAR mode, RealityView, however I didn‘t get the expected response -> User can rotate, scale the 3D models in a virtual space. ARView in nonAR mode still shows the object like in normal AR mode without camera stream. I tried to add Gestures to the RealityView on iOS - loading USDZ 3D models worked but the gestures didn’t). Model3D is only available for visionOS (that would be amazing to have it for iOS) I also checked QuickLook Preview however it works pretty strange via Filepicker etc, which is not the way how the user should load the 3D models in my app. Maybe I missed something, I couldn’t find anything which can help me. I‘m pretty much stucked adopting the latest and greatest frameworks/APIs in my App and taking the next steps porting my app to visionOS. Long story short 😃: Does someone have an idea what is the alternative to SceneView for USDZ 3D models? I appreciate your support!! Thanks in advance!
Replies
4
Boosts
0
Views
713
Activity
Jul ’25