NW.js v0.13.0-beta4 released with Chromium 48

[Roger]

http://nwjs.io/blog/v0.13.0-beta4/

We are pleased to announce NW.js 0.13.0-beta4. The major target of this release is updating Chromium to 48 branch and Node.js to latest 5.4.1. The list of changelog is short and we'll keep fixing reported issues in the following frequent releases.

Chromium 48 brings exciting changes including custom buttons in the notification; VP9 as the codec for WebRTC, seehttp://blog.chromium.org/2015/12/chrome-48-beta-present-to-cast-devices_91.html . You can use them in your NW app today.

If you're new to this major new beta version 0.13, please read http://nwjs.io/blog/v0.13.0-beta1/

ChangeLog

• Update Chromium to 48.0.2564.82
• Update Node.js to 5.4.1
• [OSX] Fix process.nextTick in some cases
• [OSX] Fix hidden window title (#4186)
• ported nw.App.fullArgv
• Fix: nw.App.quit() does nothing when use JS file as main (#4227)

Download

• http://dl.nwjs.io/v0.13.0-beta4/nwjs-v0.13.0-beta4-win-x64.zip
• http://dl.nwjs.io/v0.13.0-beta4/nwjs-v0.13.0-beta4-osx-x64.zip
• http://dl.nwjs.io/v0.13.0-beta4/nwjs-v0.13.0-beta4-linux-x64.tar.gz

SDK build:

• http://dl.nwjs.io/v0.13.0-beta4/nwjs-sdk-v0.13.0-beta4-win-x64.zip
• http://dl.nwjs.io/v0.13.0-beta4/nwjs-sdk-v0.13.0-beta4-osx-x64.zip
• http://dl.nwjs.io/v0.13.0-beta4/nwjs-sdk-v0.13.0-beta4-linux-x64.tar.gz

NaCl build and other platforms: http://dl.nwjs.io/v0.13.0-beta4/

There are 3 builds for each platform - normal build, sdk build and Nacl build. Normal build doesn't have devtools, only SDK build does. lt can be opened by pressing F12 (Cmd-Alt-I on OSX). SDK packages also have more development tools to be exposed in the following releases, as well as the NaCl support.

Our build infrastructure enables live binary build from git tip so you can access to the latest binary from http://dl.nwjs.io/live-build/

Known issues

http://docs.nwjs.io/en/latest/For%20Users/Migration/From%200.12%20to%200.13/#known-issues

[eivi...@gmail.com]

This version gets past the KDE Wallet stuff all of the previous v.0.13.0 betas stopped on for me on 64-bit Linux Mint 17 KDE, but it hangs on something different that I'm not sure what is. Here's the output to terminal:

[0118/141000:INFO:nw_package.cc(175)] ./nw
[8006:8019:0118/141009:ERROR:logging.h(808)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.kwalletd was not provided by any .service files
[8006:8019:0118/141009:ERROR:native_backend_kwallet_x.cc(411)] Error contacting kwalletd (isEnabled)
[8006:8019:0118/141010:ERROR:logging.h(808)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
[8006:8019:0118/141010:ERROR:native_backend_kwallet_x.cc(411)] Error contacting kwalletd (isEnabled)
[8006:8006:0118/141010:ERROR:logging.h(808)] Failed to call method: org.freedesktop.DBus.ObjectManager.GetManagedObjects: object_path= /: org.freedesktop.DBus.Error.UnknownMethod: Method "GetManagedObjects" with signature "" on interface "org.freedesktop.DBus.ObjectManager" doesn't exist

[8006:8006:0118/141010:ERROR:logging.h(808)] Failed to call method: org.freedesktop.DBus.ObjectManager.GetManagedObjects: object_path= /: org.freedesktop.DBus.Error.UnknownMethod: Method "GetManagedObjects" with signature "" on interface "org.freedesktop.DBus.ObjectManager" doesn't exist

I don't understand this new error, and I don't know if I should report it as a new issue, or just update the one I posted under chromium.src four days ago: https://github.com/nwjs/chromium.src/issues/59

[Ashley Gullen]

Construct 2 users are still reporting ghost process issues: https://www.scirra.com/forum/nwjs-not-completely-closing-when-exiting-app_t166669?start=40

It sounds like if a NW.js 0.12 app is upgraded to NW.js 0.13, the process fails to terminate. It sounds like another issue with corrupt AppData folders that we had on previous versions. In Construct 2, renaming the project also changes the name of the AppData folder in use, so it starts with a new empty folder and apparently that resolves the issue. Is this a known problem or should I try to narrow it down?

Ashley

--
You received this message because you are subscribed to the Google Groups "nw.js" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nwjs-general...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sinseki]

chrome.gcm.register not working in beta release.

chrome.gcm.register(["senderID"], function(e){

console.log(e);

})

> Unchecked runtime.lastError while running gcm.register: Unknown error. extensions::lastError:133

previous 0.13-alpha releases are works well.

any changes?

[Roger]

gcm is disabled by default because it send requests to Google. You can use '--enable-gcm' to enable it.

--

[Roger]

Could you please let the reporter send their app as well as the user data dir? It should be helpful to reproduce the issue. And when nw.exe refuses to quit -- how much processes of nw.exe is there (1 or 2) ?

Thanks,

Roger

[Sinseki]

Great! it works. Thanks for your help! :)

Sinseki

2016년 1월 20일 수요일 오전 10시 52분 42초 UTC+9, Roger Wang 님의 말:

[Meng]

When to add auto update?

Thanks

[3272...@qq.com]

can nw.js support for ARC Welder ? I want to use ARC Welder on the NW.JS , can it work?

在 2016年1月18日星期一 UTC+8下午5:09:50，Roger Wang写道：

[Ervin Kosch]

I would say no, not at this time. Its not officially supported and designed for the Beta version of Chrome. NW.JS is built from the production version of Chrome.

[pvbr...@gmail.com]

Hello Roger,

                    Iam automating my NW.JS desktop based web technologies implemented application using selenium web driver with java language

i see that the latest version chromedriver-nw-v0.12.3-win-x64.zip----belongs to chromedriver 2.13 version, can you please let me know what is the corresponding version for chromedriver 2.20

can i get the chromedriver-nw-vx.x.x-win-x64.zip version for chromedrive 2.20 version.

Hope you will reply to my mail.

please help me, iam struggling to automate my nw.js desktop based application,due to lack of chrome version 2.20 bundled with nw.js?

Thanks in Advance

Vijay

======================================================================

[pvbr...@gmail.com]

Hi Roger

Just forget to add the below to my earlier mail.adding it now,sorry for the inconvenience caused

Also i tried with the latest version

chromedriver-nw-v0.13.0-alpha4-win-x64.zip------chromedriver.exe----chromedriver=2.16

http://dl.nwjs.io/v0.13.0/alpha4/

this shows that for v0.13.0 the chromedriver version is 2.16, but iam looking for chromedriver version 2.20 which supports webview tags for my application

part of my logs are shown below

It shows chrome not reachable error.

Starting ChromeDriver 2.16 (bab5828ef600f00dbdbf076cb55f8070a4ac48a3) on port 16277

Only local connections are allowed.

Exception in thread "main" org.openqa.selenium.WebDriverException: chrome not reachable

  (Driver info: chromedriver=2.16 (bab5828ef600f00dbdbf076cb55f8070a4ac48a3),platform=Windows NT 10.0 x86_64) (WARNING: The server did not provide any stacktrace information)

Command duration or timeout: 61.64 seconds

Thanks,

Vijay

=============================================================

On Monday, January 18, 2016 at 2:39:50 PM UTC+5:30, Roger Wang wrote: