SkipApp-0.9.993-RC [New Wizard]

[jason]

New Wizard

This is the official release candidate of our new wizard. There are still quite a few things to do before we release this, and for visibility, I'll share below. I know it may seem like we've gone dark, but this should at least shine light on what's still needed before we're willing to say this is stable, rather than users just seeing the release 'bug fixes and improvements'. I'll update as we cross items off our list and add new ones as we find them.

 

We're extremely grateful for the help testing.

Changelog

• Improved - Wizard Add New Device

To Do

• Fix - Link in Wizard Device List should jump to record editing if it's a recorded device 11-20-24
• Manufacturer List not in alphabetical order  11-19-24
• Button List not in alphabetical order 11-19-24
• Manufacturer List Missing Recorded Devices Unless Manually Searching 11-20-24
• Search Boxes should support fuzzy searching 11-27-24
• UX - Improve search box sizes to match design 11-27-24
• UX - Improve compact mode to match design
• Search Box designs are pixels off 11-27-24
• Some icons do not match design 11-27-24
• Recording a new remote link should always be shown, not just went remote is connected  11-27-24
• Add 'Edit' Link if selected device was previously recorded.
• Don't reset settings when going back in the wizard.
• Recording Devices can't be tested in wizard  11-19-24
• Second activity should include shortcuts for previous devices
• Linux Wizard Broken 11-21-24

New Wizard

No more are the terrible drop down search bars. We have all new selections with a better search. Also gone is the useless 'test' which only does the power button. Because of the limitation of our licensed database and how datasets are grouped, it would be much more beneficial to test any of the buttons in the selected device. So now you can! 

Downloads

Mac Download
Windows Download
Linux Download

 

 

[AndrewCowley]

Does it still reset all the buttons back to their defaults when you add a new device to an existing activity?

[Kodifier]

skip-app_0.9.993+9063_amd64.AppImage
Fedora release 36 (Thirty Six)

app starts ok, finds remote. When selecting "Add Activity", entire app window goes completely white, no further activity is possible. Errors in console:

$ ./skip-app_0.9.993+9063_amd64.AppImage  

(WebKitWebProcess:175658): Gtk-WARNING **: 16:01:48.240: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size
' is not a valid property name

(WebKitWebProcess:175658): Gtk-WARNING **: 16:01:48.240: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size
' is not a valid property name

(WebKitWebProcess:175658): Gtk-WARNING **: 16:01:48.242: Theme parsing error: gtk.css:3577:25: 'font-feature-s
ettings' is not a valid property name

 

[jason]

1 minute ago, Kodifier said:

skip-app_0.9.993+9063_amd64.AppImage
Fedora release 36 (Thirty Six)

app starts ok, finds remote. When selecting "Add Activity", entire app window goes completely white, no further activity is possible. Errors in console:

$ ./skip-app_0.9.993+9063_amd64.AppImage  

(WebKitWebProcess:175658): Gtk-WARNING **: 16:01:48.240: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size
' is not a valid property name

(WebKitWebProcess:175658): Gtk-WARNING **: 16:01:48.240: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size
' is not a valid property name

(WebKitWebProcess:175658): Gtk-WARNING **: 16:01:48.242: Theme parsing error: gtk.css:3577:25: 'font-feature-s
ettings' is not a valid property name

 

Thanks for this, on it.

[jason]

2 hours ago, AndrewCowley said:

Does it still reset all the buttons back to their defaults when you add a new device to an existing activity?

Yes, this version does, good point, it's going to be fixed and I did not note that. I'll add that.

[Kodifier]

If it helps, slightly different errors on a Fedora 39 virtualbox (just had it handy, wanted to see if a later Fedora would work). Haven't managed to get the USB stuff working on it, so installed the udev rules and kept going. Get to Add Activity, same white window.  Glass half full: It's a very peaceful looking white dialog. :)

$ ./skip-app_0.9.993+9063_amd64.AppImage  

(WebKitWebProcess:2653): Gtk-WARNING **: 16:06:27.730: Theme parsing error: gtk.css:3376:25: 'font-feature-settings' is not a valid property name
Gtk-Message: 16:06:28.800: GtkDialog mapped without a transient parent. This is discouraged.

** (WebKitWebProcess:2653): WARNING **: 16:06:52.125: atk-bridge: get_device_events_reply: unknown signature

** (skip-app:2626): WARNING **: 16:06:52.621: atk-bridge: get_device_events_reply: unknown signature

 

[Kodifier]

I'm new to this (USPS just brought the remote), so I tried a previous rc. This one shows the gui and I can create an activity and sync. Going to go test with my RP5 and kodi...

skip-app_0.9.992+9040_amd64.AppImage
 

Edit: Works fine. Very nice remote. Will by another for the bedroom. The flirc usb made integration with Kodi/RP5 painless. Thanks for doing this.

Edited November 17 by Kodifier

[jason]

Updates pushed, see above for release notes / dates.

On 11/16/2024 at 2:09 PM, Kodifier said:

If it helps, slightly different errors on a Fedora 39 virtualbox (just had it handy, wanted to see if a later Fedora would work). Haven't managed to get the USB stuff working on it, so installed the udev rules and kept going. Get to Add Activity, same white window.  Glass half full: It's a very peaceful looking white dialog. :)

$ ./skip-app_0.9.993+9063_amd64.AppImage  

(WebKitWebProcess:2653): Gtk-WARNING **: 16:06:27.730: Theme parsing error: gtk.css:3376:25: 'font-feature-settings' is not a valid property name
Gtk-Message: 16:06:28.800: GtkDialog mapped without a transient parent. This is discouraged.

** (WebKitWebProcess:2653): WARNING **: 16:06:52.125: atk-bridge: get_device_events_reply: unknown signature

** (skip-app:2626): WARNING **: 16:06:52.621: atk-bridge: get_device_events_reply: unknown signature

 

We fixed some linux stuff, on the 21st.

[Aziraphale]

On Win11 the app immediately wants to update and then crashes all the time. When I re-installed it and refused the immediate update it worked, but apparently did a full reset of my Skip and now refuses to learn, so I cannot use it to control my soundbar anymore... Any ideas on how to solve this?

[jason]

On 11/28/2024 at 7:56 AM, Aziraphale said:

On Win11 the app immediately wants to update and then crashes all the time. When I re-installed it and refused the immediate update it worked, but apparently did a full reset of my Skip and now refuses to learn, so I cannot use it to control my soundbar anymore... Any ideas on how to solve this?

Sorry, which version are you using?

** Edit ** are you installing with the link in this thread?

[jason]

New update will advertise previously used devices to easily add them to new activities. A couple of bugs exist, but happy this one is finally here.

   

 

[cathalk]

At the Record step of Record Device (i.e. My Device -> Design -> Record) I get "We have had an unexpected error".

See attached screenshot + screenshot for firmware version. And last few seconds of logs.

Using MacOS Nightly build (because Record button is greyed out in 0.9.992-beta, screenshot below)

Branch: master

Pull Request: #false

CI Build: 9155

Commit: 8943d5a

react 17.0.2

react-native 0.67.4

react-native-macos 0.66.48

redux 4.2.1

react-redux 7.2.6

hidapi 0.13.1

 

Last few entries in log file at that point were:

22:11:05 <1> #USBController #ReadChunks index.js:73 * parsed the following packet metadata: {"reportId":1,"declaredSizeOrSequence":3,"isLast":true,"dataChunk":{"type":"Buffer","data":[48,56,255]}}

22:11:05 <1> #ReadChunks index.js:81 * this was the last usb packet

22:11:05 <1> #USBController #ReadChunks index.js:90 cborBuffer: {"type":"Buffer","data":[159,0,170,100,102,117,108,108,115,83,75,73,80,46,49,83,46,82,69,76,69,65,83,69,46,65,48,53,104,112,108,97,116,102,111,114,109,103,83,75,73,80,46,49,83,102,99,111,110,102,105,103,103,82,69,76,69,65,83,69,99,115,107,117,97,65,99,114,101,118,98,48,53,101,98,117,105,108,100,120,24,50,48,50,50,45,49,50,45,49,51,84,49,54,58,50,57,58,50,52,45,48,56,48,48,102,98,114,97,110,99,104,102,114,101,109,111,116,101,103,118,101,114,115,105,111,110,102,52,46,49,50,46,54,101,100,105,114,116,121,107,45,48,45,103,54,48,100,100,57,51,98,100,85,85,73,68,120,32,70,56,49,69,54,69,52,55,53,48,53,53,51,52,52,65,51,53,50,69,51,49,50,48,70,70,49,54,49,55,48,56,255]}

22:11:05 <1> #USBController #ReadChunks index.js:94 offset: 0 192

22:11:05 <1> #USBController #ReadChunks index.js:106 read usbChunks cbor result: {}.

22:11:05 <1> #USBController #WritePacket index.js:188 Final usb response: [0,{"full":"SKIP.1S.RELEASE.A05","platform":"SKIP.1S","config":"RELEASE","sku":"A","rev":"05","build":"2022-12-13T16:29:24-0800","branch":"remote","version":"4.12.6","dirty":"-0-g60dd93b","UUID":"F81E6E475055344A352E3120FF161708"}]

22:11:05 <1> #CommandProcessor #handleResponse CommandProcessor.js:49 Command: {"version":{}}. Response: {"full":"SKIP.1S.RELEASE.A05","platform":"SKIP.1S","config":"RELEASE","sku":"A","rev":"05","build":"2022-12-13T16:29:24-0800","branch":"remote","version":"4.12.6","dirty":"-0-g60dd93b","UUID":"F81E6E475055344A352E3120FF161708"}.

22:11:05 <1> #SkipApi #Learning learning.js:50 Reset learning.

22:11:05 <1> #SkipApi #Learning index.js:726 Recording for button "POWER TOGGLE".

22:11:05 <1> #CommandProcessor #Process CommandProcessor.js:64 Sending command: {"learn":{"enable":true}}.

22:11:05 <1> #USBController #Send index.js:242 Sending command.

22:11:05 <1> #USBController #CreateUsbChunk index.js:122 Creating usb send promises...

22:11:05 <1> #USBController #CreateUsbChunk index.js:136 WriteHidPacket response: {"bytesWritten":65}.

22:11:05 <1> #USBController #WritePacket index.js:178 Posted all chunks via NativeHidApi, these are the sequential USB write results: [{"bytesWritten":65}]

22:11:05 <1> #USBController #ReadChunks index.js:46 Reading a usb packet...

22:11:05 <1> #USBController #ReadChunks index.js:52 * ReadHidPacket response: {"dataHexDump":"01039f30ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff","bytesRead":65,"responseCode":0}

22:11:05 <1> #USBController #ReadChunks index.js:64 * ReadHidPacket response data: "01039f30ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"

22:11:05 <1> #USBController #ReadChunks index.js:73 * parsed the following packet metadata: {"reportId":1,"declaredSizeOrSequence":3,"isLast":true,"dataChunk":{"type":"Buffer","data":[159,48,255]}}

22:11:05 <1> #ReadChunks index.js:81 * this was the last usb packet

22:11:05 <1> #USBController #ReadChunks index.js:90 cborBuffer: {"type":"Buffer","data":[159,48,255]}

22:11:05 <1> #USBController #ReadChunks index.js:94 offset: 0 3

22:11:05 <1> #USBController #ReadChunks index.js:106 read usbChunks cbor result: {}.

22:11:05 <1> #USBController #WritePacket index.js:188 Final usb response: [-17]

22:11:05 <4> #CommandProcessor #Process CommandProcessor.js:70 600

22:11:05 <4> #CommandProcessor #handleResponse CommandProcessor.js:46 Command: {"learn":{"enable":true}}. Response: 500.

22:11:05 <4> #Learning index.js:233 Error at record signal. Code: 500.

22:11:06 <4> #RemoteConnection useRemoteConnection.js:289 Check connection error code: 504.

22:11:07 <4> #RemoteConnection useRemoteConnection.js:289 Check connection error code: 504.

Device+Firmware details

We have had an unexpected error:

flirc20241204.logflirc20241204.log

Record button is greyed out in 0.9.992-beta:

Edited December 4 by cathalk
Adding extra info

[cathalk]

Recreated Record issue using RC build 0.0.003.9152

Log sample:

23:42:14 <1> #USBController #ReadChunks index.js:73 * parsed the following packet metadata: {"reportId":1,"declaredSizeOrSequence":2,"isLast":false,"dataChunk":{"type":"Buffer","data":[110,102,52,46,49,50,46,54,101,100,105,114,116,121,107,45,48,45,103,54,48,100,100,57,51,98,100,85,85,73,68,120,32,70,56,49,69,54,69,52,55,53,48,53,53,51,52,52,65,51,53,50,69,51,49,50,48,70,70,49,54,49,55]}}

23:42:14 <1> #USBController #ReadChunks index.js:46 Reading a usb packet...

23:42:14 <1> #USBController #ReadChunks index.js:52 * ReadHidPacket response: {"dataHexDump":"01033038ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff","bytesRead":65,"responseCode":0}

23:42:14 <1> #USBController #ReadChunks index.js:64 * ReadHidPacket response data: "01033038ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"

23:42:14 <1> #USBController #ReadChunks index.js:73 * parsed the following packet metadata: {"reportId":1,"declaredSizeOrSequence":3,"isLast":true,"dataChunk":{"type":"Buffer","data":[48,56,255]}}

23:42:14 <1> #ReadChunks index.js:81 * this was the last usb packet

23:42:14 <1> #USBController #ReadChunks index.js:90 cborBuffer: {"type":"Buffer","data":[159,0,170,100,102,117,108,108,115,83,75,73,80,46,49,83,46,82,69,76,69,65,83,69,46,65,48,53,104,112,108,97,116,102,111,114,109,103,83,75,73,80,46,49,83,102,99,111,110,102,105,103,103,82,69,76,69,65,83,69,99,115,107,117,97,65,99,114,101,118,98,48,53,101,98,117,105,108,100,120,24,50,48,50,50,45,49,50,45,49,51,84,49,54,58,50,57,58,50,52,45,48,56,48,48,102,98,114,97,110,99,104,102,114,101,109,111,116,101,103,118,101,114,115,105,111,110,102,52,46,49,50,46,54,101,100,105,114,116,121,107,45,48,45,103,54,48,100,100,57,51,98,100,85,85,73,68,120,32,70,56,49,69,54,69,52,55,53,48,53,53,51,52,52,65,51,53,50,69,51,49,50,48,70,70,49,54,49,55,48,56,255]}

23:42:14 <1> #USBController #ReadChunks index.js:94 offset: 0 192

23:42:14 <1> #USBController #ReadChunks index.js:106 read usbChunks cbor result: {}.

23:42:14 <1> #USBController #WritePacket index.js:188 Final usb response: [0,{"full":"SKIP.1S.RELEASE.A05","platform":"SKIP.1S","config":"RELEASE","sku":"A","rev":"05","build":"2022-12-13T16:29:24-0800","branch":"remote","version":"4.12.6","dirty":"-0-g60dd93b","UUID":"F81E6E475055344A352E3120FF161708"}]

23:42:14 <1> #CommandProcessor #handleResponse CommandProcessor.js:49 Command: {"version":{}}. Response: {"full":"SKIP.1S.RELEASE.A05","platform":"SKIP.1S","config":"RELEASE","sku":"A","rev":"05","build":"2022-12-13T16:29:24-0800","branch":"remote","version":"4.12.6","dirty":"-0-g60dd93b","UUID":"F81E6E475055344A352E3120FF161708"}.

23:42:15 <1> #SkipApi #Learning learning.js:50 Reset learning.

23:42:15 <1> #SkipApi #Learning index.js:726 Recording for button "POWER TOGGLE".

23:42:15 <1> #CommandProcessor #Process CommandProcessor.js:64 Sending command: {"learn":{"enable":true}}.

23:42:15 <1> #USBController #Send index.js:242 Sending command.

23:42:15 <1> #USBController #CreateUsbChunk index.js:122 Creating usb send promises...

23:42:15 <1> #USBController #CreateUsbChunk index.js:136 WriteHidPacket response: {"bytesWritten":65}.

23:42:15 <1> #USBController #WritePacket index.js:178 Posted all chunks via NativeHidApi, these are the sequential USB write results: [{"bytesWritten":65}]

23:42:15 <1> #USBController #ReadChunks index.js:46 Reading a usb packet...

23:42:15 <1> #USBController #ReadChunks index.js:52 * ReadHidPacket response: {"dataHexDump":"01039f30ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff","bytesRead":65,"responseCode":0}

23:42:15 <1> #USBController #ReadChunks index.js:64 * ReadHidPacket response data: "01039f30ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"

23:42:15 <1> #USBController #ReadChunks index.js:73 * parsed the following packet metadata: {"reportId":1,"declaredSizeOrSequence":3,"isLast":true,"dataChunk":{"type":"Buffer","data":[159,48,255]}}

23:42:15 <1> #ReadChunks index.js:81 * this was the last usb packet

23:42:15 <1> #USBController #ReadChunks index.js:90 cborBuffer: {"type":"Buffer","data":[159,48,255]}

23:42:15 <1> #USBController #ReadChunks index.js:94 offset: 0 3

23:42:15 <1> #USBController #ReadChunks index.js:106 read usbChunks cbor result: {}.

23:42:15 <1> #USBController #WritePacket index.js:188 Final usb response: [-17]

23:42:15 <4> #CommandProcessor #Process CommandProcessor.js:70 600

23:42:15 <4> #CommandProcessor #handleResponse CommandProcessor.js:46 Command: {"learn":{"enable":true}}. Response: 500.

23:42:15 <4> #Learning index.js:233 Error at record signal. Code: 500.

23:42:15 <4> #RemoteConnection useRemoteConnection.js:289 Check connection error code: 504.

23:42:16 <4> #RemoteConnection useRemoteConnection.js:289 Check connection error code: 504.

23:42:17 <4> #RemoteConnection useRemoteConnection.js:289 Check connection error code: 504.`

 

[cathalk]

I've continued discussion of above Record issues on the following thread (in relation to what firmware is needed and how to get it)

 

 

[cathalk]

Record issue resolved after upgrading firmware