You will find your License Code on the WebEngage dashboard. Log in to your WebEngage dashboard and go to Account Setup section, as highlighted in the image below. Note that your License Code might start with tilde (
~), please include it as a part of the entire license code while copying.
It is the value of Info.plist key:
WebEngage SDK will automatically receive the token when it is received via APNs registration call, provided you have initialized the SDK properly.
In case you are making the APNs registration manually, you would receive the device token in your app’s AppDelegate callback
You may implement this callback for your own custom handling. WebEngage SDK automatically intercepts your callback method to receive the device token.
For manually registering your app with APNS, you need to call appropriate initialization API with the auto-register flag as
false). Refer to Initialization APIs.
Enable Verbose logging by adding
WEGLogLevel key in
Info.plist file and set its value to
Launch your app through Xcode and verify the logs. Search for the log statement: "SDK Integration Verification complete" in the Xcode console. In case it's there, your SDK integration is likely to be complete and correct, unless your configuration values are wrong. If you don't see this statement, continue with the troubleshoot.
Double-check your license code in
WEGLicenseCodekey) against the WebEngage dashboard.
If you do not find a log message saying 'SDK Integration Verification complete', you should get one saying
SDK Integration is not complete. Validations failed. You may get other specific error messages (s) before this log. In that case, act according to the instructions in the error message.
5. Users/Events not showing up in dashboard even after successful SDK integration. How do I troubleshoot?
Please go over the following checklist:
Make sure you have successfully integrated WebEngage SDK in your app.
Verify that your license code is correctly configured in your
Check the logs for the error messages "Error while reporting event to network" and "Error: Timeout occurred while waiting for events response in flush". The error messages may also provide some context of the error that occurred while trying to sync events.
Successful Event Reporting from SDK
In case events are successfully sent from the SDK, console should print a message
Reported Events to Networkin the Verbose mode. In case you observe this log on the console but events/users not showing up on dashboard, contact support at [email protected].
In case you have integrated WebEngage using CocoaPods, check the
Podfile.lock file in your project directory. This file stores the WebEngage SDK version.
For Direct Integration, look for the
Info.plist file in the WebEngage.framework directory (within the downloaded and extracted .zip file). For the WebEngage SDK version, check the file for the property named
Bundle versions string, short if viewing in the visual editor. Check for
CFBundleShortVersionString when viewing in the source code editor.
You can check this link for the latest publicly released version of the SDK.
Other than that we also make internal beta releases. Beta releases are only available through CocoaPods integration. You can get the latest beta released SDK version details here.
- If you are using CocoaPods, go to the your project director or the directory holding the Podfile in the terminal and execute:
pod update WebEngage
The command should show up the latest version being installed. Verify from here if the downloaded version is actually the latest version.
- In case the above step doesn't download the latest version of the SDK, run:
pod repo update
And then again run:
pod update WebEngage
- For Direct Integration, first check the version of iOS SDK you've installed. If you are not using the latest version, download the latest version from here and replace the existing one under
Linked Frameworks and Librariessection of the project settings. Refer Direct Integration under iOS SDK Setup.
We hope this has helped you integrate your iOS app with WebEngage. Please feel free to drop in a few lines at [email protected] in case you have any further queries. We're always just an email away!
Updated 24 days ago