The XignSys SDK and the XignIn-Manager communicate over the XignSys Protocol (also called smart-device-api). The protocol supports compatibility between different versions to some extent. The version number is based on semantic versioning and is therefore composed of MAJOR.MINOR.PATCH. The limitation are as follows:
The following three tables list the application version ranges and the supported protocol version ranges. Before updated your SDK dependency make sure the XignIn-Manager you are developing against supports the protocol version of the new SDK.
XignIn-Manager version compatibility
| XignIn-Manager Core Version | XignSys Protocol Version |
|---|---|
| 13.0.0 - ?? | 2.2.0 - 2.5.x |
| 11.0.0 - 12.1.0 | 2.2.0 - 2.4.x |
| 10.2.0 | 2.2.0 - 2.3.x |
| 10.0.0 - 10.1.0 | 2.2.0 - 2.2.x |
| 8.2.0 - 9.0.1 | 2.0.0 - 2.2.x |
| 7.5.0 - 8.1.4 | 2.0.0 - 2.1.x |
| 7.0.0 - 7.4.1 | 2.0.0 |
XignSys-Android-SDK version compatibility
| XignSys Android SDK Version | XignSys Protocol Version |
|---|---|
| 4.3.0 | 2.5.0 |
| 4.1.0 - 4.2.1 | 2.3.0 |
| 4.0.0 | 2.2.1 |
| 3.4.0 | 2.1.1 |
| 3.1.0 - 3.3.2 | 2.0.0 |
XignSys-iOS-SDK version compatibility
| XignSys iOS SDK Version | XignSys Protocol Version |
|---|---|
| 4.3.0 | 2.5.0 |
| 4.1.0 - 4.2.0 | 2.3.0 |
| 4.0.0 | 2.2.1 |
| 3.4.0 - 3.4.3 | 2.1.1 |
| 3.1.0 - 3.3.1 | 2.0.0 |
The Server Core Version of the XignIn-Manager can be retrieved by sending a http GET request to the path
/api/modules, e.g. https://xign.me/api/modules for the official XignSys XignIn-Manager. The response is
a json-object containing all active modules of the manager and their versions, for example:
JSON
{
"modules": [
{
"databaseVersion": null,
"description": "The core for the XignIn-Manager",
"name": "CORE",
"version": "10.0.1"
},
{
"databaseVersion": null,
"description": "Frontend based on Angular",
"name": "FRONTEND-WEB",
"version": "11.0.0"
}
]
}