I'm having difficulties getting AutoUpdate for an electron app to work on Windows. The app itself is working as intended on both Win and macOS, however the Auto Update provided by electron-builder only works on macOS. The update notification is properly triggered on both OS and the logs indicate that even the Win application realised that an update is available and starts the download. However, the download never seems to be completed or somehow never communicates back to the app.
One possible cause of the issue could be code signing: on macOS I am using CS with an Apple Developer Account and Auto Update works as intended. An appropriate CS cert for Win seems to be both more expensive and not even required to use Auto Updating – but this is where I'm not sure about, as I couldn't find clear answers on that: the official doc seems to imply that you dont't need it (link, "macOS application must be signed in order for auto updating to work." -> so Win doesn't?), but I found articles and sources that claimed the opposite (e.g. here or here). I don't want to purchase a certificate without knowing if that is actually causing the problem.
Can anyone give me a reliable, up-to-date (2020) answer regarding the requirement of a code signing certificate for getting Auto Updater to work on Win?
Or – does anyone have an idea what else could cause this kind of problem?
Thanks!
[edit] electron-updater log (via electron-log):
[2020-09-21 12:03:10.651] [info] Checking for update
[2020-09-21 12:03:10.698] [info] Found version 1.1.1 (url: MyApp_1.1.1_Setup.exe)
[2020-09-21 12:03:16.673] [info] Downloading update from MyApp_1.1.1_Setup.exe
[2020-09-21 12:03:16.684] [info] No cached update info available
[2020-09-21 12:03:16.690] [info] Download block maps (old: "https://{url}/MyApp_1.1.0_Setup.exe.blockmap", new: https://{url}/MyApp_1.1.1_Setup.exe.blockmap)
[2020-09-21 12:03:16.886] [info] File has 252 changed blocks
[2020-09-21 12:03:16.906] [info] Full: 47,730.39 KB, To download: 5,030.83 KB (11%)
Related
I have a question regarding Cytoscape. I just downloaded the newest version (v3.9.0) for Windows, but I am not able to open the actual application. Before I used v3.6.1 which ran perfectly fine, but I want to make use of the KEGGscape app which requires Cytoscape v3.8.0 or higher.
I have deleted the previous installation of Cytoscape, as well as made sure the cache was cleared. In addition, I downloaded the correct version of Java (Java version 11) and checked the system requirements with the script available on the website, which summarised: "Succes! You are ready to run Cytoscape 3.9.0."
So I am not exactly sure what I am missing and why it is not starting and hope anyone can help.
Thank you in advance.
Kind regards,
Sorry to hear you are having problems. When you say it doesn't start, does it correctly install, and the application doesn't start when you double-click it, or does the installer never start? If it's the former -- Cytoscape installs, but doesn't start, you could try opening up a console window and run cytoscape.bat from the directory that you installed it. That should give us more information about what the problem is. There should also be a file called framework-cytoscape.log in the CytoscapeConfiguration\3\ directory in your home. That will give us more information also.
-- scooter
I have successfully installed Cytoscape.
Version: 3.8.2
Java: 11.0.6 by AdoptOpenJDK
Java Home: /Applications/Cytoscape_v3.8.2/.install4j/jre.bundle/Contents/Home
OS: Mac OS X 10.15.6 - x86_64
I have successfully installed several apps.
However, only one of the apps JGF App shows in App drop down menu, none of the other apps seem present/active. For example, gexf-app should allow Cytoscape to import that format of file but neither 'File/Open' or 'File Import' recognize the file type.
Having read the docs, many file types are supported (seemingly) for import. However I have had no success in importing files which is arguably the most important to me at the moment.
How can I make the installed apps work or what may be preventing them from doing so?
Note: I this unanswered stackexchange question seems related.
Sorry to hear about your issues. My guess is that one of the apps you installed is crashing on startup and preventing the other apps from starting. I would start by disabling "JGF App" and "gexf-app" and see if the other apps all come up. Looking at the list of apps, you won't see them in the apps menu, though -- look in the tools menu for "Merge" and "Analyze Network". Then, you can enable gexf-app and see if it starts up (if it doesn't, you should see an indicator in the lower left-hand corner of Cytoscape). If you click it, it will give you a little more information about what happened. If that starts up fine, you can try to enable "JGF App".
-- scooter
We've recently released our app to our userbase and we are seeing a bunch of redacted exceptions in Sentry that we can't debug in any logical way.
The only thing these exceptions seem to have in common is that they never happen when the application is active:
And the available memory seems to be very low on these devices:
One theory we have is that the OS decides to close any background applications due to low memory available.
But it's quite a assumption to make at these point when I'm more inclined to believe we have made a mistake in our own code.
To my questions, how would we go about debugging these redacted exceptions? Are we right to believe that our app being closed when it's not active is no cause for concern?
The on-premise version of Sentry have several issues related to this specific problem. According to the Sentry team these will be fixed in a upcoming release for the on-premise version. But to summarize.
At first we had difficulties getting the upload scripts for the dSYMs to work. The Fastlane lane mentioned here did not work at all. Neither did the bash script that was prompted in the Sentry interface under debugging symbols.
What did work was using the sentry-cli (latest version) and bumping up the accepted file size for upload on our nginx server for our on premise. But after successfully getting our dSYMs file to actually show up in Sentry we had more problems.
The issues we've encountered are listed below:
A required debug symbol file was missing
#johan12345 Sorry for getting back to you so late. We've verified your debug symbols and can confirm they should process and symbolicate correctly. The issue you are referring to has been fixed a while back in both sentry-cli and sentry and will be available with the next release.
We have been preparing a major launch over the last couple of months which is why there have been no releases recently. However, since we've received a couple of requests regarding symbolication for on-premise customers, we will try to push a new release out soon. I cannot give you an exact timeline, though, so please stay tuned.
Again, I'm very sorry for the inconvenience this might have caused.
https://github.com/getsentry/sentry/issues/7595
Reprocessing 12 events …
Some users are reporting sometimes to be stuck on reprocessing. Mostly happens with self-installations but we also had two support issues.
This seems to be triggered by internal server errors in the processing pipeline in bad places.
Related: https://forum.sentry.io/t/stuck-there-are-x-events-pending-reprocessing/1518/6
https://github.com/getsentry/sentry/issues/5862
We've added a new button called "Discard all" which can be found above your processing issues list.
This will discard all processing issues and the corresponding events.
We've also found an error in our processing pipeline we've yet to fix.
I will close this issue for now and link new issues regarding processing errors later.
So the only thing I can advise you right now is basically deploy the master branch of Sentry because our last release was in November and we fixed a bunch of stuff since then.
Not sure if we release a new version before Sentry 9 (which still needs some time).
https://forum.sentry.io/t/ios-exceptions-shows-up-as-redacted/3681
TLDR: We are switching to Crashlytics
I need to access the sandbox directory for an application installed on an iOS device, using the command line (non-gui) from a Mac or Linux. This is to help with development and testing automation. Dropping a json file into the sandbox lets me set parameters like extra debug messages and smaller refresh intervals.
A tool like iFunBox works perfectly but is graphical only, requiring numerous clicks to do this. Emails to the developers were unanswered. It also does not support AppleScript. I did find another app that provided a Fuse module, but it turned out buggy especially if the app was uninstalled and then reinstalled (in order to reset back to first time user experience). I reported the problems to the developer but there is no fix on the horizon.
The things I need to do are:
Test if an app with a specific bundle id is installed
Create Library/Caches/MYLIBNAME directory if it doesn't exist
Copy a ~100 byte json file from the Mac to that directory
Get a copy of that file
A solution that only works from Linux is acceptable too
Devices are not jailbroken and I would prefer not to need that as a requirement
In some cases I do not have the source code to the app since it is a third party using my library, so compiling different versions of the app isn't practical.
Answer is below in many comments thanks to lxt. Summary is:
Various libraries and programs associated with libimobiledevice can solve the problems
Use patched iFuse to mount an application sandbox
Use idevicesyslog to see the console log
Use ideviceinstaller to install/uninstall apps
The various libraries and programs associated with libimobiledevice are incredibly difficult if not impossible to compile as is on Linux or Mac, and there is no unified distribution of the source or binaries
For Ubuntu try libimobiledevice (may have 3 suffix), ideviceinstaller and libimobiledevice-utils packages
For Mac a search for libimobiledevice-macosx may get you some of the way there
This is going to be a little tricky, because as I think you've found out the application name is randomly generated on every install. I don't think there is a way past that, certainly that I know of. This explains the problems you're running into when simulating a new install (...the app directory name changes to a new, random hash, and then you're stuck).
Although my preference would be to access this config file in some other way (perhaps over a network, and have some code that only executes on debug/test builds check for it), if you did want to do this then I'd suggest trying something like writing a script that when you want to simulate a new install chooses the app directory that's most recently modified. But this is very hacky.
If you're not able to insert conditional code that only executes on debug/ test builds then I think the random app naming schema that iOS uses at a file system level is going to be problematic for you whatever approach you take.
Update: Regarding iFuse and libimobiledevice - out of the box it limits you to the documents directory. This is because the authors of iFuse don't entry-level users to be confused, and also because the structure is a little different depending on iOS version. You can comment out the lines in the iFuse source - fuse_opt_add_arg(&args, "-osubdir=Documents"); - to get access to the library directory through the mount. You will obviously need to re-compile iFuse yourself if doing this.
You can make use of MobileDevice Library
I know this is an old question and I doubt anyone is looking here anymore, but I thought I'd mention that you can use 'brew install libimobiledevice' to compile on the mac. There are a lot of dependencies and Homebrew really helps make it an easy process by installing them for you.
I have installed the Zeos 7 Beta on my own machine but it fails on my client's laptop. We're both running Delphi xe2, his is Entreprise, mine is Pro. His machine is running 64-bit windows 7, mine is running Window 7 32-bit.
When I do Compile all on ZeosDbo or ProjectGoup16 it seems to get through ZCore.dpk but then shows 2 fatal errors:
ZCore.dpk(1) E2225 Never-build package 'ZCore' must be recompiled
ZParseSQL.dpk(33) E2202 Required package 'ZCore' not found
This is production code we are working on, so I hope we can find a solution and get back to working on this
Zeos forum thread: http://zeos.firmos.at/viewtopic.php?t=3633
That is one error, the 1st one. The second is merely post-effect.
Perhaps you can do better than downloading beta ZIPs: until they have mature release you just can download each day "nightly" changes by version-control tools, like Git or SVN or whatever Zeos team is using.
Such errors are usually quickly fixed (they are simple) but long released(they are so moot that no one would bother making release for them).
Just open http://zeos.firmos.at/portal.php and read where to get most instant updates and how to report problems.
Actually - there it is, http://svn.code.sf.net/p/zeoslib/code-0/trunk/
Install TortoiseSVN and be on the edge until 7.0.1 or 7.0.2 final release
The page also says: Please report bugs for this version to our brand new bugtracker on sourceforge https://sourceforge.net/p/zeoslib/tickets/
Please do. Open Source is about participating. At least participate by registering bugs.
About the essence of problem read official documentation and "See Also" section.
Someone should decide about package binary update strategy. And the decision should be kept for all packages (okay, you can mix it in some conditions, but that is not to be suggested). So basically you have three choices:
Make your own decision and put all Zeos packages into the strategy of your choice. That puts the responsibility upon yourself to maintain this fork for a while until you come back to vanilla ZeosDB.
Report the bug to ZeosDB team and ask their suggestion, then change those settings for all the packages as suggested by them.
Report the bug to ZeosDB team and wait until they'd fix it in their SVN and then do SVN Update.
Personally i'd go with 1 option, but i am ready to be FLOSS libraries co-developer.
Option 3 would be the most slow yet the most easy for you.
Option 2... well... i can not see why you should choose that, except for trying to avoid version controls at any cost, which is bad idea per se.
I also suggest you to read http://www.catb.org/esr/faqs/smart-questions.html
That would help you effectively communicate at ZeosDB forums - and you'd have to if you want to be "on the edge" (and if you do not - then wait for public release like 7.0.2).