Electron - No desktop notifications - notifications

I've been following Gary Simon's tutorial on how to make a basic app on electron, but I can't seem to get the desktop notifications working on my computer. I'm 100% sure the code is correct because I performed npm start both on my root folder and his root folder (which I downloaded from his website, performed npm install and then npm start to run his code), but I'm getting no desktop notifications. Is there a setting on my computer that's preventing it from working?
Here is a picture of what it should look like:
I checked all my notification settings on my Windows 10 machine, but everything is turned on as far as I can see.

Related

Hubspot Call provider integration

I'm trying to develop a Hubspot's Click to Call app to use by my PBX.
I've already studied the Calling Extension SDK guide and made a simple poc that works into my localhost by npm (npm start).
Now I'm trying to move into production test evinroment so, into remote server, I've basic copyed the project files and binded it by Hubspot App registration.
Unfortunatelly, when I run the app on my Hubspot TestAccount, I see (in the browser console) that it requires a "./bin/index_combined.js" file. It isn't into my npm directory and npm compiles it for me only when I run "npm start" command...(local scenario).
So how to use my Click2Call app by remote without npm ? or how to produce an index_combined.js good for remote scenario?

Unable to load script. Make sure you're either running a Metro server (run 'react-native start') or that your bundle index.android.bundle is packaged

So this has been asked before but I'm asking it again because nothing has worked, I've read through all of the similar posts I could find and all but one has semi fixed the problem.
https://medium.com/#adityasingh_32512/solved-unable-to-load-script-from-assets-index-android-bundle-bdc5e3a3d5ff
This medium article is the only solution that i can find that will get debug builds running again but that is only because it is pre packaging the javascript bundle and not really fixing the problem of the app not connecting to the metro server, once the debug build is running via this method I'm unable to shake the device and get the debug menu to show up.
I've been developing this app for probably 10 months, live for 3-4 months, and can usually trudge through these errors that pop up but this one is tricky.
I've been using cleartextTrafficPermitted="true", tried implementing a custom network security config android:networkSecurityConfig="#xml/network_security_config", tried a different physical device, cleared the metro cache, deleted .gradle/ build folders, cleaned, rebuilt.. All with the same end result of the app crashing on boot and the same error in logcat Unable to load script. Make sure you're either running a Metro server (run 'react-native start') or that your bundle 'index.android.bundle' is packaged correctly for release.
Release builds work but that's because its not trying to connect to the metro server, pretty stumped on this one.
Answering this for others that might find it useful. Still not sure what I did wrong but in the process of setting up a CI/CD pipeline for the app I re cloned the project and magically android debug builds started working again. No changes to the code, the android project must have gotten corrupted somehow so recloning allowed android studio to start from square one. Weird one.

NPM Run Start / Local Host is not loading and making my computer very slow

I am developing a react app, when I run npm run start it will not respond in the browser. (this only started happening last night, and only with this specific app. All my other projects work fine)
In windows terminal it shows a successful compile with no errors, but the localhost:3000 browser (after loading for 5 mins) shows an alert window, and it makes my computer very slow.
I uninstalled react-spring, which was the latest dependency I had installed, but it made no difference.
Any ideas or any additional info I should provide?
package.json

react-native create app hangs while create

I use react-native with actual version and have tried to create a simple project. But while trying to create it by using
expo init AwesomeProject
the whole process hangs.
I have tried to look for a solution by searching on the internet but without any luck.
The error could be seen in the following screenshot:
That error generally means that a file is being accessed by two different things at 'around' the same time. And 90% of those times it is because of an anti-virus or similar.
Its a permission error, so my advice, try to do it after a fresh reboot and boot the powershell as admin, disable antivirus etc..
If still does not work reinstall nodejs/npm.
I had the same experience. The project gets created using React-native. When you try to run it, the 'Metro' interface comes up. There is an android phone on the USB drive which has previously been used to run Android Studio created projects successfully. However, on the command shell the app hangs in Metro.
While trying to run the project from Android Studio snow cat, there are build errors (red) in the App manifest file and there is this exception.
Build failed due to java.lang.NullPointerException
Installed expo-cli (C:\Reactive-native>npm install -g expo-cli). The app fails to run and hangs on the connected Android phone(Samsung 21) using the Expo Go client. This client has no problem having been tested in Snackbar.
I have a question in the Expo forum and probably someone will answer!

Could not connect to development server in genymotion

I got an issue with Genymotion, searched and tried a lot of ways from google but could not resolved this issue. The problem is two days ago, when I was coding and testing on genymotion, everything worked fine, suddenly, no reason, the red screen showed up.
I tried to clear npm cache, run react-native run-android, react-native start, enter my local IP address to debug server host and port for device, remove node_modules and installed again, remove virtual box, remove genymotion, install all again ... Many ways I tried but no success.
Lucky me, it's still working fine in my real phone, but not really convenient to use real phone to debug.