What am trying to implement
Am new to electron. Am trying to implement releases & auto update based on channels. I followed instructions in official documentation here. I also added scripts to generate alpha build.
My Problem
Alpha build is created along with alpha.yml.
[Here is my screenshot]
(https://i.stack.imgur.com/nUin4.png).
Updater instead of looking for alpha.yml it shows an error in terminal Cannot find latest.yml in the release.
What have I tried
[Here is my package.json]
(https://i.stack.imgur.com/xuTS1.png)
The deploy command is for stable release & deploy-alpha is for alpha release. The builder-alpha.json is nothing but a copy of electron builder only difference is the product name.
[This is my main.js]
(https://i.stack.imgur.com/KVlZu.png)
I also tried keeping the appid & name as same too but that didn't work as well. I couldn't find anything more on documentation or in any search results. So any help would be appreciated. Thank you.
Related
So today I was updating one of our SPFX extensions to use the latest spfx framework (1.16) with node (16.13) and after finishing my updates I got the following inside my code:
I am not exactly sure why these are not coming in, I suspect the newest version of spfx moves these classes out of sp-application-base, but why? and where is the documentation for it? Because there is this link that is only 6 months old and explains to use this code for the top and bottom headers.
I was expecting this code to remain in sp-application-base, but it appears it isn't in that package.
How did you perform the upgrade? I highly recommend using the Microsoft 365 CLI to upgrade projects, as the developers of that app do thier best to cover every part of the project that needs to change. Learn more at https://pnp.github.io/cli-microsoft365/cmd/spfx/project/project-upgrade/
Here are the commands to run from the root of your project
npm install -g #pnp/cli-microsoft365
m365 spfx project upgrade --output text
This will give a list of npm commands and code update instructions to follow. See the above documentation for other options for output and use whatever works best for you.
It is still there. What version of #microsoft/sp-application-base is in your project? Should be 1.16.1 I believe. I will say that I am new to all of this as well, but I am using the latest framework and VS is not flagging any issues with these.
Can anyone suggest what to do about this message that I get when submitting my Xamarin Forms app to the iOS store?
Comment on possible duplicates
This question was asked before and not answered; I don't think an answered duplicate exists.
This is a known issue which was recently closed by the Xamarin team issue can be found here https://github.com/xamarin/Xamarin.Forms/issues/7323
And the fix is and i qoute
All the bits are in place, solution time! TL;DR: all is described in this piece of documentation here.
Make sure you are using the latest Visual Studio (for Mac) on the stable channel, that should put you on the right path. At the moment, you will need to use the Xamarin.Forms 4.5-pre1 preview release. I understand that this might not be an option for all of you, but rest assured, the stable package will be out well before the deadline. Stable 4.5 is planned mid to end of February.
Lastly, put the --optimize=experimental-xforms-product-type flag into your iOS additional mtouch arguments setting and you should get rid of the deprecation warning by Apple. If you don't have any references of your own to UIWebView of course 🙂
I would like to ask you to try this at your earliest convenience. Maybe not to release an actual new version to the store based on the Forms preview package, but at least upload a build to verify that this solution works correctly. Whenever you do, you can just update to the 4.5 stable package and release a new version with confidence.
If you do run into anything with this solution, please feel free to reach out to me directly (gerald.versluis [a with a long tail] microsoft.com) or open a new issue on the repository. Of course positive feedback is always appreciated as well 😉
I am trying to figure out how to force the user to use the app only if he has the last update of it( So the app should check if the local and store version are the same). I've seen this feature in some apps. Found this plugin : https://www.npmjs.com/package/nativescript-store-update. It works great on iOS but it does not work at all on Android, so I am clueless right now on how to do this. Any help would be much appreaciated. Thanks
While not sure about forcing to update the store version, you can use the newly introduced AppSync functionality to create mandatory updates for your codebase. See this blog post for details or just search for nativescript-app-sync
I downloaded go1.4.darwin-amd64-osx10.8.tar.gz and extract it on my local directory.
Based on what Installing to a custom location says I added GOROOT in env variable.
Based on what Test your installation says I created a go file.
I finally ran it and I got expected result as following screenshot.
I actually have IntelliJ v.14 however, based on this article I installed Go Language (golang.org) version 0.9.15.3 in my IntelliJ Idea.
I created a Go project and during creation it asked me to add GO SDK. I gave it ~/Desktop/go/sdk however it wasn't able to recognise it. I got this error in Event Log:
14:03:02 IllegalArgumentException: Argument for #NotNull parameter
'virtualFile' of
com/intellij/openapi/projectRoots/impl/ProjectRootContainerImpl.addRoot
must not be null
Any idea how IntelliJ Idea is able to recognize it would be appreciated. Thanks.
Please consider using one of the alpha releases for 0.9.16. I believe that alpha7 could be the more stable one rather than alpha9. You can get them from GitHub releases
The v1.0.0-alpha0 branch is, as the name implies, an alpha release and it's in the early stages of development, that's why there's no release done yet for it as well.
P.S. I'm one of the contributors to the plugin.
Does not allow to use SDK placed in /usr/local/go (perfectly valid and recent SDK) under Mac Yosemite.
Google App Engine does not recognise last valid GAE GO SDK either.
~Desktop/go/sdk doesn't seems a valid path (as it refers to the homedir of the 'Desktop' user): ~/Desktop/go/sdk should work better.
As long as you see in that ~/Desktop/go/sdk folders the subfolders 'api', 'bin', 'blog', ..., that should be the right one for the GO SDK expected by the "golang support plugin".
Some issues exist with that plugin and IntelliJ 14: issues 1169, PR 1172 (fixed for for 1.0.0-alpha).
The other approach is to recompile and install that plugin.
The end result of specifying the Go SDK path should look like:
I've succesfully generated a docset with AppleDoc by following the installation instructions. If i got into XCode Documentation Organiser, everything is there, including the categories:
But when I ⌥-click on one of my category methods I see nothing but this:
I've tried a lot of things but none of these work:
Adding --no-merge-categories
Adding --merge-categories
Changing filename extensions
Restart XCode
Restart macbook
Search google (AppleDoc quickhelp categories)
Search stackoverflow
Search gitHub repository issue list (https://github.com/tomaz/appledoc)
Please help, because I want to generate documentation, and most of my library consists of categories. I'm using the latest AppleDoc (appledoc 2.1 (build 858)), and Xcode 4.6.3.
Edit: are there users actually using AppleDoc? Does the quick help actually work for you? I also note a lack of documentation even though the repository is updated regularly.
It seems nobody else is using appledoc but me. Anyway, it looks like it is a bug in XCode, i have pushed a workaround in github. Comment if you want details.
Update: my pull request has been accepted, check here for details:
Pull request https://github.com/tomaz/appledoc/pull/375
related issue: https://github.com/tomaz/appledoc/issues/374