Agustin

@ytsejam1138 Thank you very much. The problem you experienced, and the one you're mentioning regarding autodetection, should be resolved in this version: Windows Installer.

@ytsejam1138 I have one more favor to ask. If you made changes after importing the file you shared, export the config as a backup. Then, try this version: Windows Installer Import the config file, and share your zip file. Thanks!

@ytsejam1138 Could you share the original config that you previously exported?

Create a new folder with the exact name (SkipApp) and copy the file inside.

Sorry, I haven't had my wake-up coffee yet, haha. This is the location for macOS: ~/.config/SkipApp/config.json

Close the app. Go to this folder: C:\Users\<USER>\AppData\Local\Packages\SkipApp_nk6j7xazwq5t8\LocalState Paste this file into that folder. Then, reopen the app and you'll find the Firmware tab. If you find any errors, I need to review your logs. You must send me the logs from your first attempt. But let's hope it won't be necessary and that everything turns out well. config.json

Sorry, I missed your message. If you'd like, please send me the logs and I'll review them. If not, you can use any version to update it (if you don't have the error you're seeing). Let me tell you something: this version I sent you only has a styling improvement. In other versions, if you select the item when loading the firmware, you won't notice it's selected, but the Update Firmware button will be enabled.

Sorry, the file was archived after a few hours. You can download it from this other link.

Let's try updating the firmware from the admin panel. Use this version of the app: App Link. And download this firmware file: Firmware Link. Open the app, connect the remote, and go to this section: Load the firmware I've provided, select it, and click Update Firmware. This should update the firmware on your remote and resolve the issue. If not, I'll ask you for the new logs again.

When the app detects the remote, it's in a state that prevents us from updating it. That's why there are some very important details: remove the batteries, keep the app closed while plugging it in and holding down the buttons, release them, and then reopen the app without unplugging it. Maybe you're missing one of these little details. If not, we can update the firmware from the admin panel. But let's try one more time, and if things continue the same, I'll help you update it from the admin panel.

I see your remote has firmware version 4.12.18; we need a firmware version higher than 4.13. If you followed the steps and we're still here, it's likely the update failed, as it should have been updated to 4.13.11. Let's try the steps I described to BogMan exactly, and if the error persists, please send me the new logs.

Hi Martin, how are you? The first thing I recommend is using our beta version, which you can download from our website, or our latest RC, which you can download here: https://forum.flirc.tv/index.php?/topic/18858-skipapp-09994-rc/ Try recording again and then send me your most recent log file for review. You have direct access to the logs folder here:

Thanks, BogMan. We've found the issue and will handle it in future releases. But to use your remote with the current beta, you need to do the following: 1 - Unplug the remote and close the app. 2 - Remove the batteries. 3 - Press and hold the middle button and return button while plugging in the USB-C (the remote should flash red if any button is pressed). 4 - Launch the software. You'll see the sync button say UPDATE. Click it, and your remote will receive a new firmware. After this, your remote should work normally. If not, or if you have any other issues, I'm still here to help.

Nice to meet you, too. I don't see any log of a recording attempt in this file. You can try recording and then send me the logs again?

Hi BogMan, how are you? My name is Agustin, and I'll try to help you with this. First of all, we use Human Interface Devices, so you should find the Skip1s under that category in Device Manager. Next, I understand that the problem is when trying to record. The fact that you are experiencing this error indicates that there is communication with the remote. If you add a device from our database and try to synchronize, do you get any errors? Regarding the recording: at that point, several things could be happening. I'd like to review the logs to identify the problem. You can find the logs at C:\Users\<username>\AppData\Local\Packages\SkipApp_nk6j7xazwq5t8\LocalState Could you share it with me?