Log files
Library is able to write diagnose output to the log file and also IDE console.
Application can set separate log levels for File and IDE using methods:
Ini_SetLogLevelFile(), Ini_SetLogLevelIde()
When detected some issues in the app’s/lib’s behaviour or need to get more details about sent/received request/response send us log file for review.
Copy log from IDE
It’s easiest option:
run app on device connected to computer
reproduce required usecase or issue
copy text output from the AndroidStudio(Logcat)/Xcode/VSCode console
send us for review
Get log file Windows
Just copy: C:\users\<user>\Application Data\siprix\siprix.log.
Path and name of the log file will differ when app specifed own brand name using Ini_SetBrandName()
and/or own home folder using Ini_SetHomeFolder().
- Example:
Ini_SetBrandName(ini, “MyBrand”); - log file will be saved as:
C:\users\<user>\Application Data\MyBrand\MyBrand.log.Ini_SetHomeFolder(ini, “C:\temp\”); - log file will be saved as:
C:\temp\MyBrand.log.
Get log file Android
Connect device to computer, allow debugging (which should be already done for deploy created app builds), run terminal and type command:
adb pull /storage/emulated/0/Android/data/<package_name>/files/siprix.log C:\temp\siprix.log
- Where:
<package_name> - it's your package name, like com.siprix.voip_sdk_example;
folder C:\temp or similar must already exist;
If development machine is Windows and command above displays error: ‘adb’ is not recognized as an internal or external command, but Android SDK is definitely installed try to specify full path to adb as
%LOCALAPPDATA%\Android\sdk\platform-tools\adb pull ...
Get log file iOS
Modify project’s Info.plist by adding UIFileSharingEnabled and UISupportsDocumentBrowser as shown on the image below,
build app, run, reproduce required usecase or issue and send us file, a shown on the image below.
