The toast encountered an error please make sure that the app id is set correctly

node notifier not starting #187

Am been working on an alarm clock for a while now now i will like to use notifier to notify the user but can’t fire node notifier in fact don’t even know if the way am firing it is correct. Am using a windows 8.1 tried all the read me example but none works with me please to start if someone could tell what’s wrong will be very grateful thanks
Example of one of the way i tried to fire it after the declaration
Notifier.notify( <
‘message’:’hello world ‘>);

The text was updated successfully, but these errors were encountered:

for using this you should require node-notifier in variable named Notifier, otherwise it will not work.
it is working perfectly for me, i am on windows 10.

@AshishkrGoyal thanks for the replay . just to say i require it but not still working
here is my code

const notifier = require(‘node-notifier’);
const path = require(‘path’);

notifier.notify( <
title: ‘My awesome title’,
message: ‘Hello from node, Mr. User!’,
icon: path.join(__dirname, ‘coulson.jpg’), // Absolute path (doesn’t work on balloons)
sound: true, // Only Notification Center or Windows Toasters
wait: true // Wait with callback, until user action is taken against notification
>);

just tried the examples code as i said fbut not working

@AshishkrGoyal if the calling that i did is not correct please can u give me a sample code that will work . thanks in advance

Have you tried the current master branch? Does it work there? I wonder if this might be a appID backlash (#167 et. al)

@lewatt23
you should use here JSON format for key and values,
like

const notifier = require(‘node-notifier’);
const path = require(‘path’);

notifier.notify( <
‘title’: ‘My awesome title’,
‘message’: ‘Hello from node, Mr. User!’,
‘icon’: path.join(__dirname, ‘coulson.jpg’), // Absolute path (doesn’t work on balloons)
‘sound’: true, // Only Notification Center or Windows Toasters
‘wait’: true // Wait with callback, until user action is taken against notification
>);

const notifier = require(‘node-notifier’);
const path = require(‘path’);

notifier.notify( <
title: ‘My awesome title’,
message: ‘Hello from node, Mr. User!’,
icon: path.join(__dirname, ‘coulson.jpg’), // Absolute path (doesn’t work on balloons)
sound: true, // Only Notification Center or Windows Toasters
wait: true // Wait with callback, until user action is taken against notification
>);

this code..
hope it will work for you

@AshishkrGoyal Why do you think this does anything? Both syntaxes are equally valid JavaScript, and semantically makes no difference.

@mikaelbr
because JSON format works for me but simple JS formst does not work.

I think that is coincidental, I’m afraid. There might be something else that is also different between your examples (or some computer state that is different, calling two notifications in a row for instance). But I assure you. In JavaScript context there is no difference between

All keys in JavaScript objects are strings and are coerced to strings no matter what. For instance doing:

And 1 is still made into a string. Even if it looks like an int.

Same problem here, on windows 8.1 as well — no notifications shown at all.

It seems whatever the issue is it’s with SnoreToast.exe itself? here are a few tests running it manually:

Note that on all entered commands i’m using the -w (wait) flag.

On the first attempt it did install a shortcut, apparently with the appID «Snore.DesktopToasts», then i had to crtl+c since it did seems stuck.

Then i did ran the command again using the «Snore.DesktopToasts» appID , and the program did exit straight away telling DisabledForUser — why? i do have notifications enabled, might be the appID .

On my Windows’s Notifications settings i can see an «SnoreToast» app, so i tried to run the command again using that as the appID . and the command did hang, like trying to show the notification but being unable to. no idea what’s going on here, but it’s quite frustrating.

I think this might been an issue related to appID and hopefully should be fixed in the latest version

just gave version 5.2.1 a quick try on Win 8.1 and unfortunately it’s the same, the notifications aren’t shown.

Am been working on an alarm clock for a while now now i will like to use notifier to notify the user but can’t fire node notifier in fact don’t even know if the way am firing it is correct. Am using a windows 8.1 tried all the read me example but none works with me please to start if someone could tell what’s wrong will be very grateful thanks
Example of one of the way i tried to fire it after the declaration
Notifier.notify( <
‘message’:’hello world ‘>);

Hey there! are you using Windows Ameliorated? I Believe they disabled notifications. Since i am also an ameliorated version user and i have the same issue.

Any update on fixing this? I’m getting the issue on windows 8.1 just says «The toast encountered an error.
Please make sure that the app id is set correctly.»

I encountered this issue and found out it’s because my win10 disabled app notification, just turn it on and fixed it, location is settings->通知和操作

i got this snore toast malarkey when i wanted to so a simple npm run dev for my symfony website and i must say frameworks are turning into a bigger pain then they are worth with their multiple ways of installing shit and then even needing multiple dependencies from packages that never ever match up because group A for example is building a component and then you get errors like that the framework was expecting a version 1.10 or 1.12 or 1.14 of a component but github is already on version 1.15 so you get the error that its incompatible and then you have to install even more shit by hand to get even other things that is supposed to fix shit working that it cant because other shit has security vulnerabilities so it skips the depencencies on that shit because the versions don’t match up And ALL I Actually want to do is Just Simply get CSS and Bootstrap working dangit

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Build Error — unexpected token = #2570

Description:

Running npm run development npm run watch npm run production returns an error.

static testing = false; Unexpected token = (Full error below)

I attempted to comment out that line and another error was returned:
static fakedLogs = []; Unexpected token =

Full Error: [webpack-cli] /sites/firstquoteinsurance/node_modules/laravel-mix/src/Log.js:5
static testing = false;
^

SyntaxError: Unexpected token =
at new Script (vm.js:79:7)
at NativeCompileCache._moduleCompile (/sites/firstquoteinsurance/node_modules/v8-compile-cache/v8-compile-cache.js:242:18)
at Module._compile (/sites/firstquoteinsurance/node_modules/v8-compile-cache/v8-compile-cache.js:186:36)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (/sites/firstquoteinsurance/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
at Object. (/sites/firstquoteinsurance/node_modules/laravel-mix/src/webpackPlugins/CustomTasksPlugin.js:1:73)

Steps To Reproduce:

Upgrade to laravel-mix@next, run new development script npm run development.

I’ve removed my node_modules folder, package-lock.json, and added the new scripts from upgrade.md to the package.json file.

Package.json — «devDependencies»: <
«@babel/plugin-syntax-dynamic-import»: «^7.8.3»,
«babel-plugin-lodash»: «^3.3.4»,
«babel-plugin-syntax-dynamic-import»: «^6.18.0»,
«cross-env»: «^7.0»,
«laravel-mix»: «^6.0.0-beta.10»,
«less»: «^3.12.2»,
«less-loader»: «^7.0.1»,
«resolve-url-loader»: «^3.1.0»,
«vue-template-compiler»: «^2.6.12»
>,
«dependencies»: <
«@gerhobbelt/markdown-it-attrs»: «^3.0.3-20»,
«@mdi/svg»: «^5.5.55»,
«alpinejs»: «^2.7.0»,
«axios»: «^0.19»,
«babel-plugin-webpack-alias»: «^2.1.2»,
«fontfaceobserver»: «^2.1.0»,
«lodash»: «^4.17.19»,
«markdown-it»: «^11.0.0»,
«markdown-it-container»: «^3.0.0»,
«normalize.css»: «^8.0.1»,
«tiny-slider»: «^2.9.3»,
«web-vitals»: «^0.2.4»
>

npm list —
├── @babel/plugin-syntax-dynamic-import@7.8.3
├── @gerhobbelt/markdown-it-attrs@3.0.3-20
├── @mdi/svg@5.7.55
├── alpinejs@2.7.0
├── axios@0.19.2
├── babel-plugin-lodash@3.3.4
├── babel-plugin-syntax-dynamic-import@6.18.0
├── babel-plugin-webpack-alias@2.1.2
├── cross-env@7.0.2
├── fontfaceobserver@2.1.0
├── laravel-mix@6.0.0-beta.10
├── less@3.12.2
├── less-loader@7.0.2
├── lodash@4.17.20
├── markdown-it@11.0.1
├── markdown-it-container@3.0.0
├── normalize.css@8.0.1
├── resolve-url-loader@3.1.2
├── tiny-slider@2.9.3
├── vue-template-compiler@2.6.12
└── web-vitals@0.2.4

npm ERR! peer dep missing: webpack@^4.0.0, required by friendly-errors-webpack-plugin@2.0.0-beta.2
npm ERR! peer dep missing: webpack@^4.0.0, required by webpack-dev-middleware@3.7.2

The text was updated successfully, but these errors were encountered:

Источник

lnfel/laragon-lamy

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Sign In Required

Please sign in to use Codespaces.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Automated setup for Laragon portable without dependencies.

1. Download or clone this repo
2. Run laragon.bat
3. Open the installed laragon.exe in C:laragon
4. Install the preconfigured packages via laragon menu, Right click > Tools > Quick Add > All
5. Using laragon menu, Click Menu > Apache > SSL > Enabled
6. Using laragon menu, Click Menu > Apache > SSL > Add laragon.crt to Trust Store
7. Finally run settings.bat for final setup

Everything is hard coded at the moment, and assumes the user is gonna use the default setup.

• Allow user to specify where to dump winrar, laragon portable and git portable, currently using C:UsersAdministratorDownloads
• Allow user to specify a custom packages conf file to use, currently uses the hard coded packages_conf block
• Allow user to opt in using nginx instead of deleting it by default
• (When user uses custom packages.conf sublime won’t be installed) Allow user to opt in for other text editor instead of assuming they would use sublime text
• Ask if user would like to use cmder_mini
• Test setting up Rails on Laragon (this was difficult than expected, no wonder laragon had a separate repo for rails setup)
• Prompt user to setup git username and email

• PHP 8.0.9
• Apache 2.4.48
• PHPMyAdmin 5.1.1
• MySQL 8.0.26
• Sublime 4 Portable build 4113
• Cmder mini 1.3.18
• Git Portable

Manual Steps for reference

Initial laragon setup

1. Download laragon portable, run and extract to C:laragon
2. Update C:laragonusrpackages.conf and include the packages needed to install by laragon
3. Download all using laragon menu, Right click > Tools > Quick Add > All
4. Download git portable and extract to C:laragonbingit
   • Don’t forget to set up git config —global user.name and git config —global user.email
   • git config —global init.defaultBranch main
   • git branch -m master main
5. Add sublime path to Environment PATH variable
6. Select corresponding versions for PHP, Apache, MySQL

1. This step is now moved as the final override step Using laragon menu, Right click > Apache > SSL > Enabled and Add laragon.crt to Trust Store
2. Open C:/laragon/bin/apache/httpd-2.4.48-o111k-x64-vs16/conf/httpd.conf
   • Change Define SRVROOT «/Apache24»
   • To Define SRVROOT «C:/laragon/bin/apache/httpd-2.4.48-o111k-x64-vs16»
3. Open C:/laragon/etc/apache2/httpd.ssl.conf
   • Comment out Listen 443

1. Delete laragon/data/mysql-8
2. cd to laragon/bin/mysql8.0.0.x/bin folder via cmder
3. run mysqld —initialize-insecure —console

to test run mysql -u root -p and when it asks for password just hit enter since we already removed the password on step 3.

No need to do following steps steps since —initialize-insecure initializes mysql user without a password 3. run mysqld —initialize —console (remember the password, important for step 6.) 4. run start mysqld 5. run mysql -u root -p 6. put in the password from 6. 7. You are now in mysql shell and can remove the password again: ALTER USER ‘root’@’localhost’ IDENTIFIED BY »; 8. run exit and ctrl + c the spawned tab from step 4.

1. cd C:laragonbincomposer
2. php -r «copy(‘https://getcomposer.org/installer’, ‘composer-setup.php’);»
3. php -r «if (hash_file(‘sha384’, ‘composer-setup.php’) === ‘756890a4488ce9024fc62c56153228907f1545c228516cbf63f885e036d37e9a59d27d63f46af1d4d07ee0f76181c7d3’) < echo ‘Installer verified’; >else < echo ‘Installer corrupt’; unlink(‘composer-setup.php’); >echo PHP_EOL;»
4. php composer-setup.php

Install Laravel globally

1. composer global require laravel/installer

Override laragon config [fixes ssl issue]

1. Open C:laragonbinlaragontplopenssql.conf
2. Open C:laragonusrtplopenssql.conf.tpl
3. Open C:laragonetcsslopenssql.conf
4. Change keyUsage = keyEncipherment, dataEncipherment
5. To keyUsage = nonRepudiation, digitalSignature, keyEncipherment
6. Reload Apache — Laragon will generate new SAN certificate
7. Click Menu > Apache > SSL > Add laragon.crt to Trust Store

Replace laragon cmder with updated cmder mini

Since cmder mini is installed already via laragon package that we had customized we can just rename it.

1. Rename C:laragonbincmder to cmder.bak
2. Rename C:laragonbincmdermini to cmder
3. Copy the following from C:laragonbincmder.bakvendorinit.bat

1. Then insert it into C:laragonbincmdervendorinit.bat after the following lines:

1. This should make laragon detect the updated cmder mini we just installed, to test open laragon.exe and click on Terminal button.

• Error: webpack toast encountered an error Please make sure that the app id is set correctly.
• Solution: windows settings -> Notifications and Actions (on Windows 10)
• Source: https://stackoverflow.com/questions/64949275/npm-run-dev-not-compiling-assets-with-error-notifications-for-user-are-disabled

About

Setup Laragon portable on windows using one batch script (kind of)

Источник

const mix = require('laravel-mix');
mix.sourceMaps()
/*
 |--------------------------------------------------------------------------
 | Mix Asset Management
 |--------------------------------------------------------------------------
 |
 | Mix provides a clean, fluent API for defining some Webpack build steps
 | for your Laravel application. By default, we are compiling the Sass
 | file for the application as well as bundling up all the JS files.
 |
 */

mix.js('resources/js/app.js', 'public/js')
    .react()
    .sass('resources/sass/app.scss', 'public/css');

@import 'variables';
@import '~bootstrap/scss/bootstrap';

// Body
$body-bg: #000;
$body-color: #111;


// Typography
$font-family-sans-serif: "Nunito", sans-serif;
$font-size-base: 0.9rem;
$line-height-base: 1.6;

// Colors
$blue: #3490dc;
$indigo: #6574cd;
$purple: #9561e2;
$pink: #f66d9b;
$red: #e3342f;
$orange: #f6993f;
$yellow: #ffed4a;
$green: #38c172;
$teal: #4dc0b5;
$cyan: #6cb2eb;

body {
    background: red !important;
} 

        ╷
   compiled successfully
    Notifications are disabled
    Reason: DisabledForUser Please make sure that the app id is set correctly.
    Command Line: C:MAMPhtdocssueliswebsitelaravel_ui-mainnode_modulesnode-notifiervendorsnoreToastsnoretoast-x86.exe -appID "Laravel Mix" -pipeName \.pipenotifierPipe-55288728-ce72-4ef8-82b8-0ddb58804c61 -p C:MAMPhtdocssueliswebsitelaravel_ui-mainnode_moduleslaravel-mixiconslaravel.png -m "Build successful" -t "Laravel Mix"

2 ответа

Лучший ответ

I’m getting this message when i run npm run dev or watch and I’m worried about this Reason: DisabledForUser Please make sure that the app id is set correctly.

I have imported javascript and css in the app.blade.php. Next, in the home.blade.php I’m using a div id=»app» and I’m using inside the vue component called client.vue

@extends('layouts.app')

@section('content')

<div id="app">

<cliente></cliente>

</div>


@endsection

<!DOCTYPE html>
<html lang="{{ str_replace('_', '-', app()->getLocale()) }}">
    <head>
        <meta charset="utf-8">
        <meta name="viewport" content="width=device-width, initial-scale=1">

        <title>Laravel</title>

        <!-- Fonts -->
        <link href="https://fonts.googleapis.com/css?family=Nunito:200,600" rel="stylesheet">
        <!-- Styles -->
        <style>
            html, body {
                background-color: #fff;
                color: #636b6f;
                font-family: 'Nunito', sans-serif;
                font-weight: 200;
                height: 100vh;
                margin: 0;
            }

            .full-height {
                height: 100vh;
            }

            .flex-center {
                align-items: center;
                display: flex;
                justify-content: center;
            }

            .position-ref {
                position: relative;
            }

            .top-right {
                position: absolute;
                right: 10px;
                top: 18px;
            }

            .content {
                text-align: center;
            }

            .title {
                font-size: 84px;
            }

            .links > a {
                color: #636b6f;
                padding: 0 25px;
                font-size: 13px;
                font-weight: 600;
                letter-spacing: .1rem;
                text-decoration: none;
                text-transform: uppercase;
            }

            .m-b-md {
                margin-bottom: 30px;
            }
        </style>
    </head>
    <body>
        
        <div class="flex-center position-ref full-height">
            @if (Route::has('login'))
                <div class="top-right links">
                    @auth
                        <a href="{{ url('/home') }}">Home</a>
                    @else
                        <a href="{{ route('login') }}">Login</a>

                        @if (Route::has('register'))
                            <a href="{{ route('register') }}">Register</a>
                        @endif
                    @endauth
                </div>
            @endif

            <div class="content">
                <div class="title m-b-md">
                    Laravel
                </div>

                <div class="links">
                    <a href="https://laravel.com/docs">Docs</a>
                    <a href="https://laracasts.com">Laracasts</a>
                    <a href="https://laravel-news.com">News</a>
                    <a href="https://blog.laravel.com">Blog</a>
                    <a href="https://nova.laravel.com">Nova</a>
                    <a href="https://forge.laravel.com">Forge</a>
                    <a href="https://github.com/laravel/laravel">GitHub</a>
                </div>
            </div>
        </div>
    </body>
</html>

Symptoms

Your Toast software installation keeps failing, leaving you with nothing more than a cryptic error message that states “We encountered a problem” to prod you along on your troubleshooting endeavor, this article might help.

Cause

Failure to install an app is usually caused by certain permission restrictions imposed on a user account. 

Resolution

First, you need to ensure that the points below have been properly observed:

• You are logged on to an Administrator account;
• Your antivirus software (if any) and firewall have been temporarily disabled;
• You are installing Toast on your Mac locally, not remotely;
• You have a stable Internet connection if your Toast purchase is ESD, i.e., a download;
• Your installer disc is not damaged if your purchase is physical, i.e., boxed;
• Your Mac computer meets the Toast’s minimum system requirements.

If all points have been ensured, but your Toast installation still fails with the same error message, proceed to the next section.

If your Mac is running macOS Ventura 13.xx

As the system settings have changed in this version of macOS, the procedure below applies only to macOS Ventura.

1. Open System Settings;
2. Click on Privacy & Security on the sidebar;
3. Select App Management from the right-hand panel;

   

4. See if Toast 20 Installer is listed under allow the applications below to update or delete other applications;
5. If so, make sure the switch is turned on. 

If the above procedure fixed the problem and Toast is now installed on your system, congratulations! If the install still fails, though, please proceed to the next section.

Disabling SIP

The System Integrity Protection (SIP) is one of the many security features implemented in the macOS operating system. SIP is designed to protect your Mac from malicious software or hacking. However, there are times when this security feature needs to be turned off to get an important procedure through, such as circumventing an installation that keeps failing.

It would be a good idea to first check if SIP is enabled or disabled. Follow these steps:

1. Open the Terminal app (Applications > Utilities).
2. Enter the following command and press enter: csrutil status
3. In Terminal, you can see the current status.
   

If it says SIP is “enabled”, then proceed to the next section.

How to disable System Integrity Protection in macOS

You won’t be able to disable SIP directly, as you need to boot your Mac in Recovery Mode to make this possible. Perform the steps below.

1. Turn off your Mac by going to the Apple menu and select Shut Down, then wait about 10 seconds.
2. Boot into Recovery mode by doing the following:
   • For Intel Macs: Turn on your Mac and immediately press and hold the Command (⌘) + R keys. Release the key when you see the Apple logo. 
   • For Apple M1 Macs: Press and hold the Power button and keep holding it until you see «Loading startup options«.
3. At this point, either of two things should happen, depending on whether your on an Intel or M1 Mac:
   • For Intel Macs: You should now be looking at the macOS Utilities window on your screen. In some cases, you may have to login to an admin account before being presented with the macOS Utilities window.
   • For Apple M1 Macs: Select Options (and hit Continue) > Select an admin user you know the password for.
4. From the top menu bar, click Utilities and select Terminal.
5. In Terminal enter the following command and hit enter:  csrutil disable

You will see a confirmation message in Terminal saying “Successfully disabled System Integration Protection. Please restart the machine for the changes to take effect.”

Once you have rebooted, try installing your Toast software again; it should now finish successfully. After the installation completes, do not forget to re-enable SIP to keep your computer protected.

How to re-enable System Integrity Protection in macOS

As previously stated, disabling SIP is performed only as a troubleshooting procedure. With SIP disabled, you are leaving your system vulnerable to malware and other harmful activities, such as hacker attacks. As such, you need to re-enable SIP immediately after you are done with your troubleshooting. 

To re-enable SIP, follow these steps:

1. Reboot your Mac into Recovery Mode (repeat the same steps above)
2. Open Terminal and this time, enter the following code and then hit enter:  csrutil enable
3. You will see a message saying “Successfully enabled System Integrity Protection. Please restart the machine for the changes to take effect.”

That’s about it, you are done!

How to fix the Runtime Code 192 Roxio Toast Error 192

Symptoms of Code 192 — Roxio Toast Error 192

Runtime errors happen without warning. The error message can come up the screen anytime Roxio Toast is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.

There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.

(For illustrative purposes only)

Causes of Roxio Toast Error 192 — Code 192

During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.

Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.

Repair Methods

Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.

If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.

Please note: Neither ErrorVault.com nor it’s writers claim responsibility for the results of the actions taken from employing any of the repair methods listed on this page — you complete these steps at your own risk.