Please export the package and test it on a real device.
No, it doesn't.
Please use the POST method to request data. The GET requests are currently not supported.
Response result:
{
"code": 500,
"msg": "no parameter received"
}Starting from SE iOS SDK 1.2.7.2, the delivery mode has changed to .xcframeworks. In Unity environment, only ios-arm64 is retained, otherwise compilation errors may occur.
If you want to debug using the iOS simulator in Unity environment, you need to download the iOS SDK: https://help.solar-engine.com/en/docs/b2scLf .
After decompression, replace "Assets/Plugins/iOS/framework/SolarEngineSDK.xcframework/ios-arm64" in your Unity project with "SolarEngineSDK.xcframework/ios-x86_64-simulator". Similarly, replace the Unity peoject's "Assets/Plugins/iOS/framework/SESDKRemoteConfig.xcframework/ios-arm64" with "SESDKRemoteConfig.xcframework/ios-x86_64-simulator".
Remember to switch back to "ios-arm64" when releasing the app after debugging.
Add Required SDK Dependency Frameworks:
How to add these frameworks above?
In the project directory, select TARGETS → Build Phases → Link Binary With Libraries → + → choose Security.framework, SystemConfiguration.framework, CoreTelephony.framework, AdSupport.framework, libsqlite3.dylib, AdServices.framework, and other library files.
Why and how to add the -Objc parameter?
The -Objc parameter should be added in the UnityFramework Target; otherwise the SDK initialization will fail.
Go to TARGETS → UnityFramework → Build Settings → Other Linker Flags → add -Objc.
Note:
iOS ODMInfo depends on the following frameworks:
If your project also uses Firebase features, there may be conflicts due to inconsistent dependency versions. The steps to resolve the conflicts are as follows:


If you previously integrated our Unity SDK that is not the .unitypackage format, please make sure to delete the manually placed SolarEngineSDK from your project.
Due to caching by the iOS pod command when pulling the SDK, if you want to upgrade the iOS SDK version, you need to specify the desired version or the latest version in the SDK Edit Setting panel, and then click Apply.

If you encounter this error when building and running an APK in Unity, please confirm whether the Unity project contains the corresponding .aar package for SolarEngine, for example:
com.reyun.solar.engine.xxxx.xxx.aar
Please execute a force pull:
Assets > External Dependency Manager > Android Resolver > Resolve
Assets > External Dependency Manager > Android Resolver > Force Resolve)
Root Cause:
(Applicable if using the AndroidManifest.xml provided by SolarEngine)
The launch activity declared in AndroidManifest.xml does not match the Application Entry Point set in Unity Player Settings.
For example: The manifest declares
com.unity3d.player.UnityPlayerActivity But GameActivity (new in Unity 6) is selected as the entry point in Unity Player Settings. During the build, Unity marks the unused entry activity as disabled.
Solutions:
1. Use GameActivity (for projects using UnityPlayerGameActivity as the launch entry).
Note: Unity 6 uses UnityPlayerGameActivity as the default launch entry.

Unity settings path:
Edit → Project Settings → Player → Android icon → Other Settings → Application Entry Point → Select GameActivityConfiguration in AndroidManifest.xml:
<activity
android:name="com.unity3d.player.UnityPlayerGameActivity"
android:theme="@style/BaseUnityGameActivityTheme"
android:exported="true">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
<meta-data android:name="unityplayer.UnityActivity" android:value="true" />
<meta-data android:name="android.app.lib_name" android:value="game" />
</activity>2. Use Activity

Unity Settings path:
Edit → Project Settings → Player → Android icon → Other Settings → Application Entry Point → Select Activity