My apologies — I realized I should share all of the suspicious symptoms and environment differences I found.
I also checked a few additional points that might help narrow down the cause.
Environment
Developer PC
-
UXP Developer Tool installed
-
Adobe Creative Cloud Desktop installed
-
macOS 14 → later upgraded to macOS 27 during development
-
Connected to the public internet
Deployment PC — affected machine
-
UXP Developer Tool is not installed
-
Adobe Creative Cloud Desktop is not installed
-
macOS 15
-
Fully air-gapped network
-
I assume the customer has their own Adobe license server
-
Premiere Pro was installed using an enterprise package provided by the customer’s administrator
1. Sandbox-related messages during UPIA installation
When I install the packaged UXP plugin using UPIA, I see the following messages in Console.app:
2026-09-22 12:52:10.009 I Adobe Premiere Pro 2026[masked] [com.apple.FileURL:resolve] failed to consume sandbox extension: [22: Invalid argument]
2026-09-22 12:52:10.009 A Adobe Premiere Pro 2026[masked] (CoreServicesInternal) CFURLResolveBookmarkData
2026-09-22 12:52:10.009 I Adobe Premiere Pro 2026[masked] [com.apple.FileURL:resolve] failed to consume sandbox extension: [22: Invalid argument]
2026-09-22 12:52:10.010 A Adobe Premiere Pro 2026[masked] (CoreServicesInternal) CFURLResolveBookmarkData
Something appears to be happening around sandbox/bookmark resolution, although I am not sure whether this is directly related to the WebView issue.
2. WebView initialization failure
After starting Adobe Premiere Pro and opening the UXP panel, I consistently see:
2026-09-22 12:52:16.098 Df Adobe Premiere Pro 2026[masked] (dynamic-torqnative) [Warn] [general] WebViewManager::createWebView() failed to create WebView because webViewDataStorage_ is not available
The WebView content does not render.
3. Suspicious NGL / User DT behavior
I also found some suspicious entries in an NGL log:
NGLClient_CCXProcess17.13 day.log
Component = ngl-lib SyncManager
Description = "SyncRunnable : returnStatus : 8, IsSyncAction: 0, key : User DT"
Description = "RecurringSync : Executing the pending sync for key User OS Info..."
Description = "Executing the pending sync for key User Profile..."
Description = "SyncRunnable : returnStatus: 8, IsSyncAction: 0, key : Username"
Description = "RecurringSync : SyncService stopped"
Description = "Shutdown : SyncManager shutdown"
After seeing the User DT entries, I checked the macOS Keychain with:
security find-generic-password -s "Adobe User Info" -a "User DT"
Developer PC
This returns a Keychain item.
Deployment PC
It returns:
security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.
This made me wonder whether some Creative Cloud / NGL component normally creates or manages the User DT entry, and whether the missing Adobe Desktop components on the deployment machine could be related.
4. Adobe component differences
I compared several Adobe components between the two machines.
Developer PC
The following files exist:
/Library/Application Support/Adobe/Adobe Desktop Common/ADS/ContainerBL.dylib
/Library/Application Support/Adobe/Adobe Desktop Common/RemoteComponents/RemoteCoreExts/NGLWrapper.dylib
/Library/Application Support/Adobe/Creative Cloud Libraries/CCLibrary.app
Deployment PC
The following are missing:
Adobe Desktop Common/ADS/
Adobe Desktop Common/RemoteComponents/RemoteCoreExts/
Creative Cloud Libraries/CCLibrary.app
The deployment PC does have an Adobe Desktop Common/UPI directory.
The absence of Creative Cloud Libraries itself is understandable because Creative Cloud Desktop is not installed. However, the missing ADS and RemoteCoreExts/NGLWrapper.dylib components caught my attention.
So at this point I am wondering whether the WebView failure could be related to one of these differences:
-
missing Adobe Desktop / NGL components
-
missing User DT Keychain data
-
enterprise / offline licensing initialization
-
the earlier sandbox bookmark resolution errors
I do not yet know whether these observations are actually connected, but I wanted to share them in case they help identify what webViewDataStorage_ is not available depends on internally.
Could any of these differences be relevant to UXP WebView initialization?