Develop Reference

How do I read the local storage of my Safari Web Extension using Selenium in Python?

With the Firefox WebDriver I can read the local storage of my extension like so:
extension_path = "/path/to/my/extension"
info = {
"extension_id": f"foobar",
"uuid": uuid.uuid4(),
}
base_url = f"moz-extension://{info['uuid']}/"
opts = FirefoxOptions()
opts.set_preference('extensions.webextensions.uuids', '{"%s": "%s"}' % (
info["extension_id"], info["uuid"]))
driver = webdriver.Firefox(options=opts)
driver.install_addon(extension_path, temporary=True)
driver.get(f"{base_url}_generated_background_page.html")
results = self.driver.execute_async_script((
"let done = arguments[arguments.length - 1],"
" store_name = arguments[0];"
"browser.storage.local.get([store_name], function (res) {"
" done(res[store_name]);"
"});"
), "foo")
How can I do the same with the Safari WebDriver on macOS? I've ported the extension using xcrun safari-web-extension-converter /path/to/my/extension and built and manually tested that it works in Safari. In Safari I can go to Develop -> Web Extension Background Pages -> <my web extension> to find the id of the extension and see that a generated background page is located at safari-web-extension://<id>/_generated_background_page.html
But running the following results in Selenium freezing at driver.get(f"{base_url}_generated_background_page.html")
base_url = f"safari-web-extension://<id>/"
driver = webdriver.Safari()
driver.get(f"{base_url}_generated_background_page.html")
results = self.driver.execute_async_script((
"let done = arguments[arguments.length - 1],"
" store_name = arguments[0];"
"browser.storage.local.get([store_name], function (res) {"
" done(res[store_name]);"
"});"
), "foo")
What can I do?
Update Feb 8th 2023
I have also tried an approach using browser.runtime.sendMessage where in Python Selenium I do this:
results = self.driver.execute_async_script((
"let done = arguments[arguments.length - 1],"
" store_name = arguments[0];"
" browser.runtime.sendMessage('com.oskar.foo.Extension (Apple Team ID)', {}, function (res) {"
" done(res[store_name]);"
" });"
), "foo")
and add the following to background.js in the extension:
browser.runtime.onMessageExternal.addListener(function (
request,
sender,
sendResponse
) {
browser.storage.local.get("foo").then((j) => {
sendResponse(j);
});
return true;
});
and this to the manifest.json
"externally_connectable": {
"ids": ["*"],
"matches": ["https://example.org/*"]
}
This way I actually get a value from the extension when running the test. But instead of reading the storage of the extension from the Safari instance started by Selenium, it reads the storage of the extension from the "real" safari instance.

I'm not very knowledgeable on the subject. However, such requests; It may be that it needs to provide duplex communication, including outgoing request and callback, and in this case, it may hang due to network needs.
In the link below, the transaction was made by polling with wait. I think this kind of approach can solve the problem. Also mentioned here is a bug, care it.
https://stackoverflow.com/a/28066902/914284

How can I stop IE 11/Win7 from removing ".exe" from downloade files?

I have an application which I have created an installer for. I have signed the application with a certificate. With every browser/windows combination I have tried downloading the installer works fine, except Windows 7 IE 11.
This combination strips the .exe off of the file. If I add the .exe back, the installer works fine. The file resides on the web server and I cause the download using the following JS;
function processDownload(inInstalLink, ApplicationName)
{
if (confirm("Download "+ ApplicationName + " application?"))
{
var intRandom = Math.floor((Math.random() * 10000) + 1);
window.location = inInstalLink + "?tempID=" + intRandom; //Launch alternative, typically app download.
}
}
I call the javascript above as follows;
processDownload("MyInstaller.exe", "My Fun Application")
I have read about content disposition tags, but am at a loss on how to implement them here, and not sure if they would solve the problem. Any guidance is appreciated.

This seems to be a common problem in Windows 7 IE 11 with exe downloads without a content disposition.
One solution that others have tried and had success with is appending ‘.exe’ to the url.
window.location = inInstalLink + "?tempID=" + intRandom + ".exe"
With dealing with IE compatibility, sometimes solutions aren’t as intuitive or logical as we would like them to be.

MFF 8.0 invokeProcedure ReferenceError

I'm migrating MobileFirst Web(Javascript) application developed in MFP7.1 to MFF8.0. When call a Javascript adapter, the following error happens. Does anyone give an advise how to fix the problem?
Error Message:
ibmmfpf.js:2040 Uncaught ReferenceError: extendWithDefaultOptions is not defined
at __WLClient.invokeProcedure (ibmmfpf.js:2040)
Code:
var proc = function(procedure, parameters) {
return WL.Client.invokeProcedure({
adapter: ‘XXXXXXX’,
procedure: procedure,
parameters : (parameters || [])
}, {
timeout: 60000
});
};
var standardHandler = function(res) {
if (typeof res.responseJSON === 'object' && res.responseJSON.code > 0) {
return $.Deferred().reject(res).promise();
}
return $.Deferred().resolve(res).promise();
};
//// invoking proc
return proc(‘getYYYYY’).then(standardHandler);

Some of the APIs from MFP 7.1 have been changed in MFP 8.0.Use Migration Cookbook tool.This tool helps you by identifying areas in your codebase that you will need to inspect and alter, such as APIs that are deprecated, no longer supported, or modified.
For more details about migration IBM MobileFirst Platform Foundation 6.3 - 7.1, to IBM Mobile Foundation 8.0. see below links
Migrating apps from earlier releases
Migrating apps and adapters to MobileFirst Foundation 8.0
Developing for Cordova application

0x8badf00d in React native iOS

I am developing a React Native (0.45.0) application and once in a couple of hours my application crashes (or rather gets killed by watchdog) with 0x8badf00d. I understand why watchdog kills the application; the main thread takes longer than 20 seconds to respond to an event. But I have no idea how to debug this in React Native. Everything is in Javascript and in promises so I am assuming that the network execution that I am doing is already asynchronous.
The application seems to be only crashing while it's in the background. However, the crash reports role states Foreground. We are using background fetch and background geolocation which both do a network request. I have measured the time from event trigger to finish and it does not take longer than one second in total.
I read that the most common problem for this error to happen is a network request on the main threat. Could it be that it tries to load the js bundle synchronously and hangs? How can I debug this problem when all my code is in Javascript?
Thank you very much in advance.
Incident Identifier: 36E63A5F-7C40-40C0-9914-2C9EAE494C11
Beta Identifier: 3C432B54-1947-470E-A387-6566A494E145
Hardware Model: iPhone7,2
Process: [993]
Path: /private/var/containers/Bundle/Application/70B3363C-32E9-4D26-B6C6-DB51304D46C7/.app/
Identifier: org.reactjs.native.example.Test3
Version: 20 (1.4)
Beta: YES
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Coalition: org.reactjs.native.example.Test3 [703]
Date/Time: 2017-07-17 21:31:33.1931 -0400
Launch Time: 2017-07-17 19:18:30.9574 -0400
OS Version: iPhone OS 10.3.2 (14F89)
Report Version: 104
Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace <0xF>, Code 0x8badf00d
Triggered by Thread: 0
Filtered syslog:
None found
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib
0x0000000182a07224 0x182a06000 + 4644
1 libsystem_kernel.dylib
0x0000000182a0709c 0x182a06000 + 4252
2 CoreFoundation
0x00000001839d8e90 0x1838fe000 + 896656
3 CoreFoundation
0x00000001839d6ae4 0x1838fe000 + 887524
4 CoreFoundation
0x0000000183906da4 0x1838fe000 + 36260
5 GraphicsServices
0x0000000185370074 0x185364000 + 49268
6 UIKit
0x0000000189bc1058 0x189b4c000 + 479320
7
0x00000001000bfa08 0x1000b8000 + 31240
8 libdyld.dylib
0x000000018291559c 0x182911000 + 17820
Update, symbolized part of the crash log:
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x0000000182faf224 mach_msg_trap + 8
1 libsystem_kernel.dylib 0x0000000182faf09c mach_msg + 72
2 CoreFoundation 0x0000000183f80e90 __CFRunLoopServiceMachPort + 192
3 CoreFoundation 0x0000000183f7eae4 __CFRunLoopRun + 1060
4 CoreFoundation 0x0000000183eaeda4 CFRunLoopRunSpecific + 424
5 GraphicsServices 0x0000000185918074 GSEventRunModal + 100
6 UIKit 0x000000018a169058 UIApplicationMain + 208
7 0x0000000100063294 0x10005c000 + 29332
8 libdyld.dylib 0x0000000182ebd59c start + 4

Why is WInJS included automatically when targeting Windows 8 in Cordova?

We're developing an app using AngularJS, and when we're targeting Windows 8 I noticed that the generated Visual Studio project included WinJS as a reference. Since we're not using WinJS I simply removed the reference from the project.
Then I noticed that removing WinJS caused benign script load errors in the console when running the app. Further investigation showed that cordova.js automatically checks for WinJS, and if not included tries to include it (!). Here's the relevant code:
var onWinJSReady = function () {
var app = WinJS.Application;
var checkpointHandler = function checkpointHandler() {
cordova.fireDocumentEvent('pause',null,true);
};
var resumingHandler = function resumingHandler() {
cordova.fireDocumentEvent('resume',null,true);
};
app.addEventListener("checkpoint", checkpointHandler);
Windows.UI.WebUI.WebUIApplication.addEventListener("resuming", resumingHandler, false);
app.start();
};
if (!window.WinJS) {
var scriptElem = document.createElement("script");
if (navigator.appVersion.indexOf("Windows Phone 8.1;") !== -1) {
// windows phone 8.1 + Mobile IE 11
scriptElem.src = "//Microsoft.Phone.WinJS.2.1/js/base.js";
} else if (navigator.appVersion.indexOf("MSAppHost/2.0;") !== -1) {
// windows 8.1 + IE 11
scriptElem.src = "//Microsoft.WinJS.2.0/js/base.js";
} else {
// windows 8.0 + IE 10
scriptElem.src = "//Microsoft.WinJS.1.0/js/base.js";
}
scriptElem.addEventListener("load", onWinJSReady);
document.head.appendChild(scriptElem);
}
else {
onWinJSReady();
}
I guess my main question is, should I just leave the WinJS reference "as is" and let Cordova load and initialize WinJS?
Could it potentially conflict with AngularJS or reduce the performance of the app in any way?
(I guess var app = WinJS.Application and app.start() in onWinJSReady makes me a bit worried).
Since the app seems to work fine without the WinJS script files, why is cordova.js so insistent on trying to include it?

cordova (and some cordova plugins, particularly the FileSystem plugin) use some features of WinJS, such as Promises and Ajax calls. We ended up forking cordova.js and stripping out all the WinJS stuff... makes the app load a lot faster!