[iOS] Qonversion SDK making requests to malformed URLs - missing API hostname

[lukeholmgren]

Note: This issue was constructed with the assistance of AI analysis of native iOS logs.

Environment

• Platform: iOS (all versions)
• SDK Version: @qonversion/react-native-sdk@10.0.0-RC2
• React Native: 0.81.5
• Expo: 54.0.21

Description

The Qonversion SDK is attempting to make HTTP requests to incomplete/malformed URLs that are missing the API hostname. This causes DNS resolution failures on iOS.

Root Cause

The SDK is constructing URLs like:

• https://v1/user/init
• https://v3/users/QON_3ec1e2018a9a4c419b5c33dc59996f46/properties

Instead of properly formed URLs like:

• https://api.qonversion.io/v1/user/init
• https://api.qonversion.io/v3/users/QON_3ec1e2018a9a4c419b5c33dc59996f46/properties

Error Details

Error Domain=NSURLErrorDomain Code=-1003 "A server with the specified hostname could not be found." NSErrorFailingURLStringKey=https://v1/user/init _NSURLErrorNWResolutionReportKey=Resolved 0 endpoints in 2ms using unknown from cache

The DNS resolver is unable to find a hostname for v1 because it's not a valid domain.

Stack Trace

Task .<2> HTTP load failed Error Domain=NSURLErrorDomain Code=-1003 "A server with the specified hostname could not be found." NSErrorFailingURLStringKey=https://v1/user/init NSErrorFailingURLKey=https://v1/user/init

Reproduction Steps

1. On any iOS device
2. Call Qonversion.initialize() with valid project key
3. Observe: Network error with malformed URLs in logs

Expected Behavior

The SDK should construct complete, valid URLs with the proper API hostname (e.g., api.qonversion.io).

Actual Behavior

The SDK constructs incomplete URLs missing the hostname, causing DNS resolution failures.

Key Observations

• ✅ Works on Android (likely uses different URL construction or has fallback logic)
• ❌ Fails on iOS (malformed URLs)
• The issue is in the SDK's URL construction logic, not in the app's configuration
• The project key and configuration are correct (user ID is generated: QON_3ec1e2018a9a4c419b5c33dc59996f46)

Possible Root Causes

1. Missing API Base URL Configuration - The SDK may not be properly initializing the base URL for API requests
2. Platform-Specific URL Construction - iOS implementation differs from Android
3. Configuration Issue - Base URL not being set during initialization
4. SDK Bug - URL construction logic is stripping the hostname

Workaround

None available - this is a critical SDK issue that prevents initialization entirely.

[NickSxti]

Hello, lukeholmgren!
Could you provide relevant Qonv_UID or project_ID for further investigation?
We don't see the given user (QON_3ec1e2018a9a4c419b5c33dc59996f46) being created.

[lukeholmgren]

Sorry I think AI may have made that Qonv_ID up. This is the project=ZFowW2u7 from url or do you require Project Key?

This issue is happening on initialize()

[github-actions]

This issue is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[EvgOcheredko]

I'm experiencing the same issue with malformed Qonversion API URLs.

Environment

• React Native: 0.79.4 (Expo dev build)
• Qonversion SDK: @qonversion/react-native-sdk 10.0.0-RC2
• iOS + Android

Issue
After initializing the SDK, all requests go to: https://v1/user/init (instead of https://api.qonversion.io/v1/user/init)

Workaround
Downgrading back to react-native-qonversion 9.0.3 immediately fixes the malformed URL issue,
but this version does not support the new NoCodes screen preloading.

[github-actions]

This issue is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[devantti]

Same issue also here. Tested on both 10.0.0-RC2 and 10.0.0.

[NickSxti]

Hello!
Sorry for the delayed response to the case.
We have found a possible root that causes this error and are currently investigating it.
I'll keep you updated and get back in the thread as soon as there is any news.

[NickSxti]

Hello!
This issue is caused by multiple initializations of the Qonversion SDK.
In a simplified version
`useEffect(() => { const qonversionConfig = new QonversionConfigBuilder( process.env.EXPO_PUBLIC_QONVERSION_PROJECT_KEY ?? '', LaunchMode.SUBSCRIPTION_MANAGEMENT ) .setEnvironment(Environment.SANDBOX) .setEntitlementsCacheLifetime(EntitlementsCacheLifetime.WEEK) .build()

Qonversion.initialize(qonversionConfig)
setIsInitialized(true)
console.log('Qonversion initialized')
}, [isInitialized])`
Will be triggered multiple times for every isInitialized parameter changed.

As a solution, you can:

Leave empty brackets for []

Add a (!isInitialized) check before initialization

[github-actions]

This issue is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days.