Could please someone help me to fix this issue? I'm trying to update my project, but I'm having problems with firebase deploy. Or rather the deploy goes fine, but I can't see my project on the browser I always receive this message:
Firebase Hosting Setup Complete
You're seeing this because you've successfully setup Firebase Hosting. Now it's time to go build something extraordinary!
OPEN HOSTING DOCUMENTATION
The messages that I receive after running firebase deploy
i deploying hosting
i hosting[webpage-1ffe0]: beginning deploy...
i hosting[webpage-1ffe0]: found 49 files in dist/webpage
✔ hosting[webpage-1ffe0]: file upload complete
i hosting[webpage-1ffe0]: finalizing version...
✔ hosting[webpage-1ffe0]: version finalized
i hosting[webpage-1ffe0]: releasing new version...
✔ hosting[webpage-1ffe0]: release complete
✔ Deploy complete!
My domains on Firebase page
webpage-1ffe0.web.app
default
webpage-1ffe0.firebaseapp.com
default
www.webpage.com
redirect
And my firebase.json
{
"hosting": {
"public": "dist/webpage",
"ignore": [
"firebase.json",
"**/.*",
"**/node_modules/**"
],
"rewrites": [
{
"source": "**",
"destination": "/index.html"
}
]
}
}
Related
I am using the Swift Package Manager that is built into Xcode 13.1 (not the command line version that uses Package.swift).
One of my dependencies is a Binary-only package. Here is what the Package.swift of that package looks like:
// swift-tools-version:5.5
import PackageDescription
let package = Package(
name: "MyLibrary",
products: [
.library(
name: "MyLibrary",
targets: ["MyLibrary"]),
],
dependencies: [],
targets: [
.binaryTarget(
name: "MyLibrary",
url: "https://gitlab.example.com/api/v4/projects/85/packages/generic/mylibrary/1.0.1/MyLibrary.xcframework.zip",
checksum: "..."
)
]
)
The binary is stored in GitLab's Generic Package Repository.
I have added the Git repository that hosts the package to my "Package Dependencies" in my project. I have generated a Personal Access Token that has API and Repository access and added it to my .netrc file:
machine gitlab.example.com
login gitlab-token
password MY_TOKEN_HERE
When I run xcodebuild -resolvePackageDependencies or use "File" -> "Packages" -> "Resolve Package Versions" in the Xcode GUI, the Git repository is cloned successfully but I get the following error message:
failed downloading 'https://gitlab.example.com/api/v4/projects/85/packages/generic/mylibrary/1.0.1/MyLibrary.xcframework.zip' which is required by binary target 'MyLibrary': badResponseStatusCode(401)
I have tried adding the same credentials to the macOS Keychain to see if Xcode can pick them up from there, but I still see the same error.
In the Swift Package Manager CLI source code, I can see that it handles crednetials for binary downloads too, but it seems that Xcode does not.
Unfortunately, I cannot switch from Xcode-integrated packaging to Package.swift packaging because other developers on the project will be confused by it.
Is it possible to get Xcode to use the .netrc credentials for downloading the file too?
Note: Cross-posted to Apple Developer Forum
When I run the Flutter web app in Android Studio using the run button or by flutter run -d Chrome, everything works just fine.
When I run flutter build web and open $(project_dir)/build/web/index.html, I get a white screen. There are these errors in the browser console:
Failed to load app from a service worker. Falling back to plain <script> tag. index.html:85:21
Loading failed for the <script> with source “file:///main.dart.js”. index.html:1:1
When I run flutter build web -v there is following:
[ +68 ms] Skipping target: web_entrypoint
[ +1 ms] Skipping target: gen_localizations
[ +311 ms] Skipping target: dart2js
[ +10 ms] invalidated build due to missing files:
/home/vanousek/prg/substance-mix/DOES_NOT_EXIST_RERUN_FOR_WILDCARD954977783
[ +72 ms] web_release_bundle: Starting due to {InvalidatedReasonKind.inputMissing: The following inputs were
missing: /home/vanousek/prg/substance-mix/DOES_NOT_EXIST_RERUN_FOR_WILDCARD954977783,
InvalidatedReasonKind.inputChanged: The following inputs have updated contents:
/home/vanousek/prg/substance-mix/build/web/main.dart.js,build/web/index.html}
[ +121 ms] Manifest contained wildcard assets. Inserting missing file into build graph to force rerun. for
more information see #56466.
When building your flutter app for web it's intended to be run on a web server.
Running flutter build web, would compile the project into a web project. You can use web hosting providers such as netify, firebase hosting, and Github pages.
Running the ./build/web/index.html would not show up. That's why you got the errors in the console.
You could run flutter run --release -d chrome to run on Chrome in release mode.
EDIT:
This is chrome DevTools, it seems that the site was looking for the main.dart.js and other resources.
I noticed it was pointing towards https://your_url/main.dart.js but the resource is located in https://your_url/substance_mix/main.dart.js. So it threw 404's.
One solution to this is to edit the index.html and add /substance-mix/ to all resources. Eg. change scriptTag.src = 'main.dart.js'; to scriptTag.src = 'substance_mix/main.dart.js';
or you can the GitHub Pages configurations. And have your website directly on https://mikulasvanousek.github.io/
I am new to ionic framework, facing below issue while creating first app.
**i am working behind corporate proxy
-> command executed “ionic start hello_ionic tabs”
Error Message :
? The directory hello_ionic contains file(s) that could conflict. Would you like to overwrite the directory with this new project? Yes
√ Creating directory .\hello_ionic - done!
√ Downloading and extracting tabs starter - done!
? Would you like to integrate your new app with Cordova to target native iOS and Android? Yes
√ Personalizing ionic.config.json and package.json - done!
ionic integrations enable cordova --quiet
√ Downloading integration cordova - done!
√ Copying integrations files to project - done!
[OK] Added cordova integration!
Installing dependencies may take several minutes.
IONIC DEVAPP *
Speed up development with the Ionic DevApp, our fast, on-device testing mobile app
Test on iOS and Android without Native SDKs
LiveReload for instant style and JS updates
️ –>Install DevApp:
npm i
Running command
ionic start stuck at “npm i”.
please help me in resolving this issue.
->output of “npm info”
{ name: ‘hello_ionic’,
description: ‘a’,
‘dist-tags’: { latest: ‘1.0.0’ },
versions: [ ‘1.0.0’ ],
maintainers: [ ‘gboog andersonthomas603#gmail.com’ ],
time:
{ modified: ‘2017-04-19T13:42:30.205Z’,
created: ‘2017-04-19T13:42:30.205Z’,
‘1.0.0’: ‘2017-04-19T13:42:30.205Z’ },
homepage: ‘https://github.com/WebGExecutive/app#readme’,
keywords: [ ‘sss’ ],
repository:
{ type: ‘git’,
url: ‘git+https://github.com/WebGExecutive/app.git’ },
author: ‘Griffin Blotner’,
bugs: { url: ‘https://github.com/WebGExecutive/app/issues’ },
license: ‘ISC’,
readmeFilename: ‘’,
version: ‘1.0.0’,
main: ‘index.js’,
scripts: { test: ‘s’ },
dist:
{ shasum: ‘73936188b9f38359107be3fce56da2643d195a89’,
tarball: ‘https://registry.npmjs.org/appapp/-/appapp-1.0.0.tgz’ },
directories: {} }
npm i does not works with Proxy.
You can refer to following links -
npm does not work behind corporate proxy and launched from apm
https://www.c-sharpcorner.com/article/how-to-use-npm-install-the-command-behind-corporate-proxy-server/
I am batting to get a successful build on IonicJs when I push my code up to the Ionic Git remote.
My application sits in a subfolder on the root directory of my repository. At first when I execute “npm run build” on the root the build process was telling me it could not find my package.json file. After reading the ionic docs (https://ionicframework.com/docs/pro/basics/concepts/customizing-builds.html) I noticed that in the case of an app being in a sub folder you need to place another package.json file in the root of your repository. I did this and the above error was solved and the build process worked on my local machine. But when I push the changes up to the Ionic Js for building it tells me that its “Missing ionic.config.json in app.”
Here is the package.json file I placed in the root of my repository.
{
"author": "",
"name": "io.cordova.myappe070fb",
"private": true,
"version": "0.1.0",
"scripts": {
"install": "cd App && npm install",
"build": "cd App && .\\node_modules\\.bin\\ionic-app-scripts build --prod"
}
}
`
My questions:
Is there a way to configure the package.json file in the root of the repository so that when Ionic runs “npm run build” it will build based on the package.json file in the App folder.
How do I solve the problem regarding the missing ionic.config.json error that is being generated by ionic.
Kind regards
Andrew
I am trying to package my app with electron-forge package using the following configuration:
"config": {
"forge": {
"make_targets": {
"linux": [
"deb"
],
"win32": [
"squirrel"
]
},
"electronPackagerConfig": {
"asar": false,
"dir": "./src",
"platform": [
"linux",
"win32"
],
"arch": [
"ia32",
"x64"
],
"ignore": [
".idea"
]
}
}
}
The version of electron-forge I am using is 3.0.1.
Only the values asar and ignore are recognized, while dir, platform and arch are ignored. I do not see an error and would highly appreciate help, a hint or a link to any working example.
Update:
It has since been suggested here to use the command line for providing these options.
While
electron-forge package --arch=ia32,x64 --platform=win32,linux
does package the app for all the specified systems, although the output looks like this:
✔ Checking your system
✔ Preparing to Package Application for arch: ia32,x64
✔ Compiling Application
✔ Preparing native dependencies
✔ Packaging Application
✔ Preparing to Package Application for arch: x64
✔ Compiling Application
✔ Preparing native dependencies
✔ Packaging Application
✔ Preparing to Package Application for arch: armv7l <-- ???
✔ Compiling Application
✔ Preparing native dependencies
✔ Packaging Application
✔ Preparing to Package Application for arch: x64
✔ Compiling Application
✔ Preparing native dependencies
✔ Packaging Application
It does not seems to actually be packaging the app for the armv7l architecture as it says there, I think that this is just a bug with the console output, the results in the output directory look good.
Anyway.. providing the packaging options via command line does not solve my initial problem, because I still can not specify the dir option for electron-packer that way. So, while the documentation for electronPackagerConfig suggests all options for electron-packer can be set with this configuration object:
This config object provides options directly to electron-packager, the tool we use to package your app behind the scenes.
And while electron-forge package --help says I can set the current working directory after the options:
Usage: electron-forge-package [options] [cwd]
Which is actually not the case, this just simply sets the out directory where everything is written to.
I am still stuck with this. Is there any way to provide the dir option via electron-forge? If not, my suggestion to the developers of electron-forge would be to implement the configuration for this in a way that makes my initial configuration from above work, because I think this is an intuitive way to configurate these parameters, using the command line to override them could still be an option, I guess.