* initial Detox setup for mobile UI automation
* fix iOS allow permission on opening the app, add npm script to root folder, fix test when using longer site URL and add detox dependency to root for android build dependency
* remove detox proguardFile
* update packages and emulator
* change folder build on local and CI
* add test to post a message, ability to have test in isolation, server API commands, server config, dependency updates and update folder structure
* update snapshot
* update detox and do clean up
* update dependencies
* Upgrade to RN 0.63
* Bump to RN 0.63.1
* Fix RN patch
* Use JSC Intl version
* Update android/app/build.gradle
Co-authored-by: Miguel Alatzar <migbot@users.noreply.github.com>
* Fix Android external storage permission
* Fix emoji imageUrl when no server url is present
* Patch react-native-image-picker
* Allow to post attachment only messages
Co-authored-by: Miguel Alatzar <migbot@users.noreply.github.com>
* MM-24328: Show Press again to exit toast when back button on Channel screeen is pressed.
* Fix feedbacks.
* Handle back press only for the Channel screen.
* MM-24328: Add a back press handler to share activity.
* Update the toast message as Press back again to exit.
* Don't retry nor use response message on 401
* Explicitly call contentHandler on retry exhaustion
* Handle all non 200 responses for id_loaded notifications
Co-authored-by: Elias Nahum <nahumhbl@gmail.com>
* MM-22181 Backoff retries for ID-loaded push notification messages
Fibonacci backoffs. 6 attempts in ~20 seconds, not including response latency for each failure.
0 seconds to attempt 1 (original try)
1 seconds to attempt 2
2 seconds to attempt 3
3 seconds to attempt 4
5 seconds to attempt 5
8 seconds to attempt 6
* PR review: Reset re-request counter when server call succeeds
* PR Review: Localize scope of recursion counter
This handles scenario where multiple notification requests are being made at the same time for multiple messages. Counter will be isolated for each fetch request.
* PR Review: Remove unnecessary class variable
* Trigger Build
Co-authored-by: Miguel Alatzar <this.migbot@gmail.com>
Users are hitting legitimate exceptions when using the Android Share extension.
However, in some cases where the channel ID isn't available from the user's actions that triggered the exception, the Sentry error reporting message payload can't be successfully formed and it bombs.
This commit allows Sentry's payload to be successfully formed, so that we can now see the actual underlying exception (with its associated user data) in Sentry. The single, catch-all `NoSuchKeyException` should now stop, and be replaced by a few new Sentry exception reports to analyze and tackle individually.
* Upgrade Navigation library
* Feedback review on Navigation Library
* Fix select server background color
* Fix iPhone 11 and 11 Pro Max navbar height
* Fix background color on Select Server
* Upgrade nav lib to 6.1.0
* Apply patch to nav lib
* Upgrade RNN to 6.1.1
* Reacting to shift-enter events on iOS
* moving keyEvent logic to handleHardwareEnterPress
* configured android to work with keyEvents
* using dispatchKeyEvent instead of onKeyUp
* using react-native-hw-keyboard-event
* cleanup
* updated package name
* update package name
* using react-native-hw-keyboard-event v0.0.2
* reverted cocoapods version change
* Documentation
* fix detection of Shift-Enter on android
* simplify dispatchKeyEvent()
* fix for stacked hardware keyboard events
* Update android/app/src/main/java/com/mattermost/rnbeta/MainActivity.java
Co-Authored-By: Miguel Alatzar <migbot@users.noreply.github.com>
* simplify dispatchKeyEvent
* removed yarn.lock
* using react-native-hw-keyboard-event v0.0.4
* Using ACTION_UP instead of ACTION_DOWN
Co-authored-by: Miguel Alatzar <migbot@users.noreply.github.com>
* Don't use localPath when it's the share extension cache dir
* Move android pasted images to cache image folder
* Use Files.move instead of FileInput / FileOutput stream
* Remove commented code and not needed imports
