Release v6.4.1

usabilla · Oct 14, 2019 · 93efecb · 93efecb
1 parent 9937425
commit 93efecb
Show file tree

Hide file tree

Showing 4 changed files with 14 additions and 3 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,9 @@
+## 6.4.1
+#### Fixed
+- Crash caused by TargetingOptionsModel when obfuscated
+- Crash when the `body` in `UsabillaHttpResponse` is null
+- Compatibility with dynamic feature modules
+- EditText losing text on rotation
 ## 6.4.0
 #### Added
 - User can draw on the screenshot to mask or highlight features

diff --git a/README.md b/README.md
@@ -65,7 +65,7 @@ Our SDK uses the following dependencies. If your project doesn't use them alread
 dependencies {
     implementation 'com.android.volley:volley:1.1.1'
     implementation 'com.android.support:appcompat-v7:28.0.0'
-    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.3.41"
+    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.3.50"
 }
 ```
 
@@ -558,8 +558,13 @@ To do so a couple of steps are required:
     ```
 
 ## Permissions
-If the user tries to set a custom screenshot, the SDK will ask for the permission to access the external storage.    
-No other permission is needed to run the SDK.
+The SDK uses the following permissions:
+```
+<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
+<uses-permission android:name="android.permission.CAMERA" />
+```
+These permissions are only needed during the flow in getting a new screenshot. The SDK can capture pictures directly or get from the image gallery.
+This flow lets users of the SDK annotate the image that was captured.
 
 ## Accessibility
 In order to have Android TalkBack work properly with the passive feedback form, you have to make sure that the `Activity` (or `Fragment`) holding the `FormClient.fragment` received from our SDK stops being considered for TalkBack.

diff --git a/ubform-6.4.0.aar b/ubform-6.4.0.aar
diff --git a/ubform-6.4.1.aar b/ubform-6.4.1.aar