I am trying to implement app authenticity on android native app. It works fine I am able to get fail on app authenticity failure .. But the problem is I am getting an error saying .
Unexpected errorCode occurred. Please try again.
But what I am expecting is. I was seeing this error before yesterday, But from yesterday I am seeing "Unexpected errorCode occurred. Please try again.". I took an update can that be a cause.
app authenticity security check failed
And I am also seeing below error, even before fail is being called.
07-27 05:30:02.392 15664-15664/com.ds I/MultiDex: VM has multidex support, MultiDex support library is disabled.
07-27 05:30:02.392
15664-15664/com.ds I/MultiDex: install
07-27 05:30:02.392
15664-15664/com.ds I/MultiDex: VM has multidex support, MultiDex
support library is disabled.
07-27 05:30:02.448 15664-15686/com.ds
W/com.worklight.common.Logger:
com.worklight.common.Logger.setContext(Context) must be called to
fully enable debug log capture. Currently, the 'capture' flag is set
but the 'context' field is not. This warning will only be printed
once.
07-27 05:30:03.493 15664-15670/com.ds W/art:
Suspending all threads took: 149.185ms
I was checking the value(App authenticity failure message) by
calling wlFailResponse.getErrorMsg() which was giving me
"Unexpected errorCode occurred. Please try again."
But the actual value(App authenticity failure message) that i am looking for
was in wlFailResponse.getResponseJSON().getString("reason").
Related
We have different WebView workflows for our App. I'm able to switch context for the Workflows which has contexts NATIVE_APP, WEBVIEW_com.bluebird.mobile and WEBVIEW_Terrace (3 contexts),
And not able to switch context for the workflows which has only two context NATIVE_APP and WEBVIEW_Terrace. While switching the context I get the following error:
Appium error: An unknown server-side error occurred while processing the command.
Original error: An unknown server-side error occurred while processing the command.
Original error: unknown error: Failed to get sockets matching: #weblayer_devtools_remote_.*14722
(make sure the app has its WebView/WebLayer configured for debugging)
(Driver info: chromedriver=105.0.5195.52 (412c95e518836d8a7d97250d62b29c2ae6a26a85-refs/branch-heads/5195#{#853}), platform=Linux 5.16.7-200.fc35.x86_64 x86_64)
When I look on the internet for the error "make sure the app has its WebView/WebLayer configured for debugging", I see solution to set setWebContentsDebuggingEnabled to true and we already set this configuration because some of the workflows are working.
Please let me know what I need to do here? OR what can I ask my DEV team to fix this.
I am trying to deploy a smart contract on a private blockchain on ethereum network. But it gives me this error" Error: *** Deployment Failed ***
"Migrations" -- invalid sender."
Now I have done some reading and saw the problem is with the version of "truffle hdwallet provider".
This is the response that I get after installing npm inside directory which shows that hdwallet is installed but still i get this error.
Even if i install another version of hdwallet provider I get the same error as seen below:
I dont understand what am i missing here. If someone can help i will be greatfull. Thanks
Problem solved. It was not actually the problem with truffle hdwallet but the version of truffle. Truffle 5.2.6 was giving me that error and it works fine with truffle 5.0.0.
I'm suddenly seeing the following on Crashlytics for a macOS app, and this seems to happen only on macOS 10.14. I have no idea what this is. What's deferredCurrentActivation and how do I avoid this? Anyone else seen this?
Fatal Exception: NSInternalInconsistencyException
deferredCurrentActivation already set when we got another deferred activate event
My Android react-native app is crashing with an ExecutionException.
"Could not connect to development server."
The method that is crashing is ReactInstanceManagerImpl.createReactContext().
But this is not the normal error as this screenshot shows:
Logcat shows me this stacktrace:
Exception in native call from JS
java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException:
Could not connect to development server.
at com.facebook.react.ReactInstanceManagerImpl.createReactContext(ReactInstanceManagerImpl.java:860)
at com.facebook.react.ReactInstanceManagerImpl.access$700(ReactInstanceManagerImpl.java:98)
at com.facebook.react.ReactInstanceManagerImpl$ReactContextInitAsyncTask.doInBackground(ReactInstanceManagerImpl.java:194)
...
Caused by: java.util.concurrent.ExecutionException: java.lang.RuntimeException:
at com.facebook.react.common.futures.SimpleSettableFuture.get(SimpleSettableFuture.java:68)
at com.facebook.react.ReactInstanceManagerImpl.createReactContext(ReactInstanceManagerImpl.java:831)
... 9 more
Caused by: java.lang.RuntimeException:
at com.facebook.react.bridge.ReactBridge.loadScriptFromFile(Native Method)
at com.facebook.react.bridge.JSBundleLoader$2.loadScript(JSBundleLoader.java:58)
at com.facebook.react.bridge.CatalystInstanceImpl.runJSBundle(CatalystInstanceImpl.java:148)
at com.facebook.react.ReactInstanceManagerImpl$4.call(ReactInstanceManagerImpl.java:851)
...
This suggests that the server has sent the javascript code back to the device and the ReactBridge.loadScriptFromFile() somehow can't handle the bundle.
Points to clarify:
this happens on emulator & device (connected via USB)
this happens on Linux (Mint) & Windows (8.1)
I did run adb reverse tcp:8081 tcp:8081 as per the normal advice
I have run react-native start and the packager/server is running
the device DOES connect to the development server, as this is logged in the packager window
the URL that the device hits does return data, as can be seen if copied into the browser address bar
How is this different from the normal "Could not connect..." message?
Here is a screenshot of what happens when the server is legitimately not running:
The differences include:
no ExecutionException or RuntimeException before the error message
further clarity providing the URL that was called on the server
error comes from DevServerHelper.onFailure()
Logcat shows the stacktrace to be quite different in this normal expected case:
Unable to download JS bundle
com.facebook.react.devsupport.DebugServerException:
Could not connect to development server.
at com.facebook.react.devsupport.DevServerHelper$1.onFailure(DevServerHelper.java:196)
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:140)
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
This seems to have been caused by not having Windows Build Tools correctly installed. This broke the node-gyp commands required by my project.
Following the steps on the node-gyp page got my machine set up correctly.
After a new build I got this error once, and then it disappeared with the project building and running correctly.
How to resolve this below issues while capture screen in IE?
I have registered the snapsie.dll in C:\Windows
Error Detail:
"Error: Snapsie failed: Is it installed? Does it have permission to run as an add-on? See http://snapsie.sourceforge.net/"