NetSparkle logs showing error (404) trying to perform an update check

A place to report problems and bugs in SharpCap
Forum rules


If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs

Please also read about Troubleshooting USB Issues before posting.

*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***

Please include the following details in any bug report:

* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
Post Reply
jcinaz
Posts: 12
Joined: Sun Jan 27, 2019 12:50 am

NetSparkle logs showing error (404) trying to perform an update check

#1

Post by jcinaz »

$ cat NetSparkle\ 20-01-20--03-26-53.log
[8:26:53 PM.577] Using the following url: https://links.sharpcap.co.uk/updates/3.2.x64.xml
[8:26:53 PM.580] Starting background worker
[8:26:53 PM.594] Starting update loop...
[8:26:53 PM.595] Reading config...
[8:26:53 PM.599] Downloading and checking appcast
[8:26:54 PM.615] Error during app cast download: The remote server returned an error: (404) Not Found.
[8:26:54 PM.616] No version information in app cast found
[8:26:54 PM.616] Sleeping for an other 1440 minutes, exit event or force update check event

This happens a LOT. The URL mentioned in the first line DOES NOT EXIST!
Using SharpCap 3.2 Pro (v3.2.6195, 64 bit), Windows 10 Pro (v1903, build 18362.592).
User avatar
admin
Site Admin
Posts: 13330
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: NetSparkle logs showing error (404) trying to perform an update check

#2

Post by admin »

Thanks for the notification - I guess that means that autoupdate is not working at all for the 64 bit version. I thought I had fixed it in a different way (not needing the .x64 in the URL), but maybe I left the .x64 in the URL by mistake - I will check on my return home from my current trip.

thanks,
Robin
Post Reply