Develop Reference

Original error: 'POST /element' / 'GET /session/bda49419-373f-4ae8-8d8e-1537553bf008/source' cannot be proxied

After the tap by coordinates action used by W3C, I am trying to call the driver again to find the element and that's when it throws the error.
When I use driver.getpageSource(), it gives me the below error.
GET /session/bda49419-373f-4ae8-8d8e-1537553bf008/source' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
When I directly call driver.findElement(), it gives me this error.
An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
Build info: version: '4.6.0', revision: '79f1c02ae20'
I was trying to automate the app using the Appium and first step was to call the driver.findElements and then I went to tap by coordinates using w3c actions (PointerOptions),and after the above step, I had driver.findElement() and it gave me the above errors.

EXPO publish fail. What is the cause?

I have tried to publish my expo app so I can get started on the release process but publish keeps failing with the following error. What is the issue?
Publishing to channel 'default'...
Request failed with status code 404
Error:
Request failed with status code 404
at createError (C:\Users\tade2\AppData\Roaming\npm\node_modules\expo-cli\node_modules\axios\lib\core\createError.js:16:15)
at settle (C:\Users\tade2\AppData\Roaming\npm\node_modules\expo-cli\node_modules\axios\lib\core\settle.js:17:12)
at IncomingMessage.handleStreamEnd (C:\Users\tade2\AppData\Roaming\npm\node_modules\expo-cli\node_modules\axios\lib\adapters\http.js:237:11)
at IncomingMessage.emit (node:events:406:35)
at endReadableNT (node:internal/streams/readable:1331:12)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

You need to update expo-cli - you are using a version that lesser than 1 year and above old and points to a no longer existing endpoint checkout issues with below link .
https://docs.expo.dev/bare/error-recovery/

HMS: Getting error in push notification token with error code 907135003

I'm new to flutter, Unable to get the token from Huawei push notification in flutter.
I'm using below code to get data:
await Push.getToken("");
await initTokenStream();
Unable to get the token from huawei push notification in flutter. Getting error in push notification token with error code 907135003
Log
E/HMSSDK_HmsInstanceId( 5742): TokenTask failed, ErrorCode: 907135003 D/HMSLogger( 5742): singleEventMap -> {apiName=getToken, package=com.bghuawei.app, cpAppVersion=1.0.0, version=5.3.0.304, platform=Flutter, result=907135003, costTime=218, service=Cross-Platform, kit=Push, appid=105282649, model=OP4F2F, networkType=WIFI, callTime=1641433679625} I/HMSSDK_BaseHmsClient( 5742): Enter disconnect, Connection Status: 5
Can any one help me !! Thanks

Please refer to the URLs below for the error code description and solution. Please try to use the latest version of HMS Core per Shirley's comment above as well.
https://developer.huawei.com/consumer/en/doc/development/HMSCore-References/error-code-0000001050255690
https://developer.huawei.com/consumer/en/doc/development/HMSCore-Guides/error-code-0000001050994177

error code 907135003
This error is reported when the HMS Core version is too early and needs to be upgraded. Therefore, pls try to upgrade the HMS Core apk to the latest version.

MobileFirst 8.0 Direct Update not work and the app keep loading

Good day,
I upload a web resource archive to MobileFirst Console, I expected my mobile device will receive the direct update notification.
However, my app just keep loading.
I go check the mfp trace.log, it just keep printing
[3/9/20 19:52:01:788 MYT] 000000c1 id= com.worklight.common.util.JNDIUtils 1 JNDI Access (global scope) not found in cache for key mfp.cloud.devicelimit
[3/9/20 19:52:01:789 MYT] 000000c1 id= com.worklight.common.util.JNDIUtils 1 globalScopeLookup JNDI Access via globalScopeLookup to mfp.cloud.devicelimit => null
I try to google on this error message but didnt get any good result.
I run the following command to generate the web resource file:
mfpdev app webupdate --build
And then I upload it to MFP Console.
My cordova-plugin-mfp version is as follow:
"cordova-plugin-mfp": "^8.0.2020012903"
Its Cordova app.
There is no client side log, the console just log nothing until it hit timeout, then it only log timeout message.
Any Ideas?

Android: Handle App Link Verification failure at install time

I added app link feature with autoVerify set for my app following link
On testing the app, it worked in the begining. Then after reinstalling the build, not working.
On debugging what I found is the response time for my .well-known/assetlinks.json file is > 1sec.
which gives timeout error on test-url https://digitalassetlinks.googleapis.com/v1/statements:list?source.web.site=https://example.com&relation=delegate_permission/common.handle_all_urls
{
"maxAge": "599.999999353s",
"debugString": "********************* ERRORS *********************\n* Error: deadline_exceeded: Timeout occurred while fetching Web statements from https://example.com./.well-known/assetlinks.json (which is equivalent to 'https://example.com/.well-known/assetlinks.json') using download from the web (ID 1).\n********************* INFO MESSAGES *********************\n* Info: No statements were found that match your query\n"
}
Looks like because of this timeout, verification is failing.
I would like to know whether app/system retry verification at any point later if verification failed on install (may be because of connection issue or temporary website down)?

Unfortunately Android M does not automatically reattempt verification if it fails due to timeout or connectivity issues. As you found in this guide the next attempt will occur on app update or re-install.