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.
Related
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.
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/
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?
I created ibm-mobilefirst-starter:latest container in bluemix. And I am able to access the MFS console.I can see MobileFirstStarter run time its working fine. Now I uploaded new .wlapp and one http .adapter file into MFS console and they are visible in Console. When I try to access the Adapter from Common Resources I am getting Error :
[http://134.168.31.10:9080/MobileFirstStarter/authorization/v1/clients/preview] failure. state: 404, response: The server was unable to process the request from the application. Please try again later.
Client registration failed with error: {"responseHeaders":{"Date":"Tue, 01 Mar 2016 12:35:44 GMT","Connection":"Close","X-Powered-By":"Servlet/3.0","Content-Length":"0","Content-Language":"en-US"},"status":404,"responseText":"","errorCode":"UNEXPECTED_ERROR","errorMsg":"The server was unable to process the request from the application. Please try again later.","invocationContext":null}
I tried with Android environment and tested in device. Couldn't see any response from adapter.
Thanks in Advance.
There is no preview available from the console in non-development environments (i.e. MobileFirst Studio plug-in for Eclipse).
It is unclear from your question if only the preview failing or also from a device/emulator.
I have a unity project for android which is larger than 50MB and so must be split. I have had working apt splitting for a couple months now. Starting a few days ago I mad a couple changes which were purely aesthetic. I uploaded the new build and now(days after the api and obb files were uploaded) I receive an error at the download point on the device "Download failed because the resources could not be found."
I manually added the obb file to the device and it worked, I have tried re uploading the apk and bob files with minor changes and still after a day of waiting see the same errors.
viewing with logcat I see these errors when i try to download
I/LicenseChecker(20270): Binding to licensing service.
W/ContextImpl(20270): Implicit intents with startService are not safe: Intent { act=com.android.vending.licensing.ILicensingService } android.content.ContextWrapper.bindService:517 com.unity3d.plugin.downloader.c.j.a:-1 com.unity3d.plugin.downloader.b.s.run:-1
I/LicenseChecker(20270): Calling checkLicense on service for [my project com]
I/LicenseChecker(20270): Start monitoring timeout.
W/GLSUser (26959): GoogleAccountDataService.getToken()
I/qtaguid (18936): Failed write_ctrl(u 53) res=-1 errno=22
I/qtaguid (18936): Untagging socket 53 failed errno=-22
W/NetworkManagementSocketTagger(18936): untagSocket(53) failed with errno -22
I/ElegantRequestDirector(18936): I/O exception (org.apache.http.NoHttpResponseException) caught when processing request: The target server failed to respond
I/ElegantRequestDirector(18936): Retrying request
I/LicenseChecker(20270): Received response.
I/LicenseChecker(20270): Clearing timeout.
Its not obvious to me what I did to make obb downloading stop working. I don't know enough about the error messages to pick anything out of it.
What can I do to make it download the bob files again?
In case anyone else runs into this here was my solution. It looks like Google made a policy change.
"To test your application's implementation of the manual download procedure, you can publish it to the alpha or beta channel, so it will only be available to authorized testers. If everything works as expected, your application should begin downloading the expansion files as soon as the main activity starts.
Note: Previously you could test an app by uploading an unpublished "draft" version. This functionality is no longer supported; instead, you must publish it to the alpha or beta distribution channel. For more information, see Draft Apps are No Longer Supported."
so now you need to publish your alpha/beta builds before you can download the files.