How does 'Always Send' option after enabling prompt in Crashlytics work? Enabling the prompt feature will display a prompt with three options after crash on next launch- Send, Always Send and Don't send of which Always Send does not seem to work for me for ios
Do we need to provide some kind of implementation or it should work by default.
Related
Recently, whenever I'm printing a file from IE, I'm getting a prompt to save or open the file before printing. I tried to disable this prompt under security tab-Custom level-Downloads in Internet option but I'm not able to find the option to disable the automatic prompt. This started happening from last week.
I'm using Internet Explorer 11.
Please let me know if anyone has any idea why the option is not visible or anyway to disable this prompt and directly send file to printer.
I am not sure Which kind of file you are trying to print. But it looks like that file format is not supported by the IE browser.
Generally, when you try to open the file that is not supported by the IE browser it will show you that prompt and give you the option to save or open that file.
If we talk about that prompt then at present there is no way to disable that prompt.
In the older versions of the IE browser has the option to disable this prompt. In those older versions, there was a way to disable this prompt using the registry key. For security purposes, these options were removed in the IE 10 and IE 11 version.
I suggest you use the dedicated application for that file type and try to print the file from that application.
For example, if you want to print the word document then try to use MS Word application to print it.
I'm trying to write a selenium test which :
Connect to a website (which prompt an authentication window)
Click on "cancel" of the authentication window
Do some test stuffs...
But my problem is that : I am not able to cancel the authentication step.
My test should not depend on the environment (I don't want to change the Windows registry keys)
I found this chromium command "--auth-server-whitelist=..." that automatically fills and submit this prompt and I am looking for something that would always refuse the authentication.
Any Ideas ? Suggestions of better ways ?
I need to authenticate to a website.
After successful authentication - a form is shown, where a few details are filled.
After submitting the form, the page gives an impression that something is loading:
After a non-fixed delay, a download pop up is shown:
Sadly, assuming if I try to download from URL, I cannot overcome the authentication part. The web browser client is authenticated, not the VBA client.
My simple question is:
How to detect, whether this download pop up has appeared or not in IE9+?
A few things I have tried:
URLDownloadToFile is of no use, since the download link for the file is not fixed and appears after authentication
Siddharth's answer, does not addresses IE 9 download dialogue box, rather works for IE 8 dialogue box
I believe that after successfully detecting this pop up, I can download the file to local disk simply using SendKeys - correct me if needed.
Side question: how to download the file to local disk after detection is successful?
I'm using worklight application management features from an Android native App.
I want that when in the console the application status is changed to "Access Disabled" the only option for the user will be to quit.
In the Knowledge Center and in Developer works there is documentation about how to do it:
http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.appadmin.doc/admin/t_denying_access_to_older_app_versions.html?lang=en
https://www.ibm.com/developerworks/community/blogs/worklight/entry/how_to_create_a_customized_remote_disable_behavior?lang=en
It is explained that you must set a specific value for the initOptions object used in the WL.Client.init() method.
But in the Android native API I have not found the way to set the initOptions. The init method is deprecated and it does not accept initOptions.
Also, in case of Remote Disable the ResponseListener used in the WLClient.connect(aResponseListener) is not invoked, success or failure, no method is executed. Is this working as designed? I would expect a failure or success but not nothing.
Is it possible in a native app to force the application to close in case of Remote Disable?
How could I handle this situation manually in the app?
Unfortunately I do not have an example for you, but this is the general idea.
See if you can work with it (if someone can produce an example - please do...):
You need to create your own Remote Disable challenge handler that will extend the default Worklight Remote Disable challenge handler (RemoteDisableChallengeHandler.java).
class MyRemoteDisableChallengeHandler extends WLRemoteDisableChallengeHandler
Then you need to implement your custom logic in MyRemoteDisableChallengeHandler
WLClient.registerChallengeHander(new MyRemoteDisableChallengeHandler())
This will override the original.
You'll need to create your own dialog with a Quit button.
Some additional documentation.
For handling MaM configurations, this is, when you configure the app as Lost, Stolen, etc, in the Worklight Console -> Devices tab you must install the Fix IF201408281937 (Worklight 6.2) or later.
This events are also handled with the ChallengeHandler registered for the realm "wl_remoteDisableRealm"
Using the Worklight v5.0.6 code sample/tutorial "Integrating server-generated pages in hybrid applications" (http://public.dhe.ibm.com/software/mobile-solutions/worklight/docs/v506/WebViewOverlay.zip) allows for the web content to be integrated. The code sample works fine and web content integrated correctly.
However, when I set connectOnStartup to true in the apps//common/js/initOptions.js file, the tabs and web content from the WebViewOverlay fail to load.
I see in the wlclient.js (apps//android/native/assets/www/default/wlclient/js/wlclient.js) that there is a check that if doConnectionOnStartup is true, then call WL.Utils.wlCheckReachability(), else call finalizeInit()
It appears that the WebViewOverlay and the tabs are created by the finalizeInit() being called, but if connectOnStartup is set true, then finalizeInit is not called.
How can I get both the WebViewOverlay to work and the connectOnStartup to work together?
This is, most probably, caused by connection failure. wlCommonInit function will be invoked only after successful connection, in case connection fails it will never be invoked. First of all - check your connectivity from a mobile handset to WL server. Second, you can either manually use WL.Client.connect() after tabbar was initialized (like Carlos suggested) or specify onConnectionFailure callback in your initOptions.
I provided what I did above in the comments - but it turned out that the dialog box to indicate an update was available was not showing up, and instead the error message "WL.SimpleDialog.show() error in invoking callback." was seen in the log messages of logcat. This log message is coming from worklight.js (apps//android/native/assets/www/default/wlclient/js/worklight.js) on line 820. Just FYI, I did change the worklight.js code to print out err, and it said "No class found". I didn't take the troubleshooting any further at that point
So the app was contacting the WL Server correctly, but the dialog to indicate an update was available was not appearing.
To fix, I simply created a new hybrid app and brought over the necessary code to get the WebViewOverlay to work