@athaandr wrote:
Hi!
I would like to ask you whether it would be possible to use the ion-picker controller in a form, where the picker selections will not appear in a dialogue but directly on the page where the form is located.
Posts: 1
Participants: 1
@gaiapuffo wrote:
Hi, I have a ionic 4 application.
I have to color the icon of the select but on the guide https://ionicframework.com/docs/api/select?fbclid=IwAR30w0w4kXeNSiLbIXT7-eCg-I53ZygVJok0j29AGU0zSnBesthstSScJr0#css-custom-properties there are only 4 css properties…So I try to put in my scss file.select-icon-inner{color:red!important}but this not working …Is possibile that exist only 4 rules css for the select???
Posts: 1
Participants: 1
@Tubiss wrote:
json api like this.
{“data”:[{“id”:2,",“start_time”:“2019-06-26 00:00:00”,}]}
how can ı make order by start time.
my provider like this.
return new Promise(resolve => {
this.http.get('http://127.0.0.1:8000/xxx') .map(res => res.json()) .subscribe(data => { // we've got back the raw data, now generate the core schedule data // and save the data for later reference this.data = data.data; resolve(this.data); }); });}
page.ts like this
public people: any;
constructor(
public rService : RProvider,public http: Http,) {
//this.getData();
this.loadPeople();
}loadPeople(){
this.remoteService.load()
.then(data => {
console.log(data);
this.people = data;});
}so please help me how can ı make order depend on start time.
Posts: 1
Participants: 1
@Liquidcms wrote:
The starting page for my app has 3 icons and a chart (drawn using chart.js). This page also does a redirect to the login page if a user object is not available in storage. I am having difficulty understanding the timing here as i have 2 different timing related problems.
- the icons and the chart (depending on how chart is displayed) are shown briefly before the page is redirected.
OR
- the empty div for the chart is not available when i go to embed my chart.
my latest code attempt looks like this:
ionViewWillEnter() { if (jDrupal.user.uid === '0' || jDrupal.user.uid === '0') { this.show = false; this.router.navigate(['user/login']); } else { this.show = true; } } ionViewDidEnter() { this.show = true; this.showChart(); } showChart() { const canvas: any = document.getElementById('myChart'); if (canvas === null) { return; } const ctx = canvas.getContext('2d'); const myChart = new Chart(ctx, {... static chart data }the above seemed like an easy solution but clearly i do not understand the timing of this relative to the template being loaded.
The other approach i had tried was to set the value of “Show” and then use it in the template with *ngif to hide contents before switching. this way i only flash a blank page; but this also does not work.
Perhaps my flaw is how the redirect is being done?
Posts: 1
Participants: 1
@Jonnnn wrote:
Our company is trying to use the android phone as a server with SMS functionality, may I ask how to do this?
I am currently using the nativeSMS from the docs but it always needs permission when sending an SMS
would appreciate any feedback
Posts: 1
Participants: 1
@uptownjimmy wrote:
We implemented a new app with ion-split-pane and realized that there is a problem only on iPad Pro. I am assuming it has something to do with that being screen size where the split pane kicks into gear?
The menu toggle button doesn’t work, and the left side of the screen is a large white block. As soon as I comment out the ion-split-pane tag, the problem goes away.
Posts: 1
Participants: 1
@BizzyBob wrote:
I’m using an
<ion-list>with<ion-sliding-item>'s. The inner item has a(click)event(click)="goToDetail(message.id)".<ion-list #messageList> <ion-item-sliding *ngFor="let message of messages"> <ion-item detail (click)="goToDetail(message.id)"> <ion-label> {{ message.text }} </ion-label> </ion-item> <ion-item-options> <ion-item-option (click)="confirmDelete(message.id)">Delete</ion-item-option> </ion-item-options> </ion-item-sliding> </ion-list>Normally, when the item is clicked, I want the click event to fire.
However, if I slide one of the items, revealing the ‘Delete’ option, then click on a different item, the sliding item closes, then the (click) event of the other item is fired.
I want to prevent this click event. I’ve read the documentation and see the
<ion-list>has acloseSlidingItems()method. So, I was hoping I could simply change my click event to something like:(click)="messageList.closeSlidingItems() || goToDetail(message.id)"But, the closeSlidingItems() method returns a promise, not a boolean. Okay, no problem, I thought to just wrap my
goToDetail()function with this check.public goToDetail(threadId) { this.messageList.closeSlidingItems() .then(sliderWasClosed => { if (!sliderWasClosed) { this.nav.navigateForward('app/conversation/' + threadId); } }); }However, what I’m finding is that the promise always returns
false, even when a sliding item is in fact closed. I suspect this is because the close operation happens automatically and by the time my function is called, the item is already closed.My overall goal is to prevent the
(click)event when sliders are open. My current code would work if thecloseSlidingItems()method would return the proper value.Is there a way I can prevent this automatic closing of sliding items in order to get the correct result when I call
closeSlidingItems()myself?Is there another event I should be using besides
(click)?Any other ideas how I can get this to work?
Posts: 1
Participants: 1
@RodrigoCoolnect wrote:
$ ionic start teste7 blank
√ Creating directory .\teste7 - done!
[INFO] Fetching app base (https://github.com/ionic-team/ionic2-app-base/archive/master.tar.gz)
√ Downloading - done!
[INFO] Fetching starter template blank (https://github.com/ionic-team/ionic2-starter-blank/archive/master.tar.gz)
√ Downloading - done!
√ Updating package.json with app details - done!
√ Creating configuration file ionic.config.json - done!
[INFO] Installing dependencies may take several minutes!npm install
× Running command - failed!
[ERROR] An error occurred while running npm install (exit code 1):npm WARN deprecated @angular/http@5.0.0: Switch to @angular/common/http - see https://angular.io/guide/http npm WARN deprecated sw-toolbox@3.6.0: Please migrate to Workbox: https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-sw npm WARN deprecated browserslist@2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm WARN deprecated mixin-deep@1.3.1: Critical bug fixed in v2.0.1, please upgrade to the latest version. npm WARN deprecated set-value@2.0.0: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm WARN deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. > node-sass@4.5.3 install D:\0 - PROJETOS\teste7\node_modules\node-sass > node scripts/install.js Downloading binary from https://github.com/sass/node-sass/releases/download/v4.5.3/win32-x64-64_binding.node Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.3/win32-x64-64_binding.node": HTTP error 404 Not Found Hint: If github.com is not accessible in your location try setting a proxy via HTTP_PROXY, e.g. export HTTP_PROXY=http://example.com:1234 or configure npm proxy via npm config set proxy http://example.com:8080 > uglifyjs-webpack-plugin@0.4.6 postinstall D:\0 - PROJETOS\teste7\node_modules\uglifyjs-webpack-plugin > node lib/post_install.js > node-sass@4.5.3 postinstall D:\0 - PROJETOS\teste7\node_modules\node-sass > node scripts/build.js Building: C:\Program Files\nodejs\node.exe D:\0 - PROJETOS\teste7\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library= gyp info it worked if it ends with ok gyp verb cli [ 'C:\\Program Files\\nodejs\\node.exe', gyp verb cli 'D:\\0 - PROJETOS\\teste7\\node_modules\\node-gyp\\bin\\node-gyp.js', gyp verb cli 'rebuild', gyp verb cli '--verbose', gyp verb cli '--libsass_ext=', gyp verb cli '--libsass_cflags=', gyp verb cli '--libsass_ldflags=', gyp verb cli '--libsass_library=' ] gyp info using node-gyp@3.8.0 gyp info using node@10.16.0 | win32 | x64 gyp verb command rebuild [] gyp verb command clean [] gyp verb clean removing "build" directory gyp verb command configure [] gyp verb check python checking for Python executable "python2" in the PATH gyp verb `which` failed Error: not found: python2 gyp verb `which` failed at getNotFoundError (D:\0 - PROJETOS\teste7\node_modules\which\which.js:13:12) gyp verb `which` failed at F (D:\0 - PROJETOS\teste7\node_modules\which\which.js:68:19) gyp verb `which` failed at E (D:\0 - PROJETOS\teste7\node_modules\which\which.js:80:29) gyp verb `which` failed at D:\0 - PROJETOS\teste7\node_modules\which\which.js:89:16 gyp verb `which` failed at D:\0 - PROJETOS\teste7\node_modules\isexe\index.js:42:5 gyp verb `which` failed at D:\0 - PROJETOS\teste7\node_modules\isexe\windows.js:36:5 gyp verb `which` failed at FSReqWrap.oncomplete (fs.js:153:21) gyp verb `which` failed python2 { Error: not found: python2 gyp verb `which` failed at getNotFoundError (D:\0 - PROJETOS\teste7\node_modules\which\which.js:13:12) gyp verb `which` failed at F (D:\0 - PROJETOS\teste7\node_modules\which\which.js:68:19) gyp verb `which` failed at E (D:\0 - PROJETOS\teste7\node_modules\which\which.js:80:29) gyp verb `which` failed at D:\0 - PROJETOS\teste7\node_modules\which\which.js:89:16 gyp verb `which` failed at D:\0 - PROJETOS\teste7\node_modules\isexe\index.js:42:5 gyp verb `which` failed at D:\0 - PROJETOS\teste7\node_modules\isexe\windows.js:36:5 gyp verb `which` failed at FSReqWrap.oncomplete (fs.js:153:21) gyp verb `which` failed stack: gyp verb `which` failed 'Error: not found: python2\n at getNotFoundError (D:\\0 - PROJETOS\\teste7\\node_modules\\which\\which.js:13:12)\n at F (D:\\0 - PROJETOS\\teste7\\node_modules\\which\\which.js:68:19)\n at E (D:\\0 - PROJETOS\\teste7\\node_modules\\which\\which.js:80:29)\n at D:\\0 - PROJETOS\\teste7\\node_modules\\which\\which.js:89:16\n at D:\\0 - PROJETOS\\teste7\\node_modules\\isexe\\index.js:42:5\n at D:\\0 - PROJETOS\\teste7\\node_modules\\isexe\\windows.js:36:5\n at FSReqWrap.oncomplete (fs.js:153:21)', gyp verb `which` failed code: 'ENOENT' } gyp verb check python checking for Python executable "python" in the PATH gyp verb `which` failed Error: not found: python gyp verb `which` failed at getNotFoundError (D:\0 - PROJETOS\teste7\node_modules\which\which.js:13:12) gyp verb `which` failed at F (D:\0 - PROJETOS\teste7\node_modules\which\which.js:68:19) gyp verb `which` failed at E (D:\0 - PROJETOS\teste7\node_modules\which\which.js:80:29) gyp verb `which` failed at D:\0 - PROJETOS\teste7\node_modules\which\which.js:89:16 gyp verb `which` failed at D:\0 - PROJETOS\teste7\node_modules\isexe\index.js:42:5 gyp verb `which` failed at D:\0 - PROJETOS\teste7\node_modules\isexe\windows.js:36:5 gyp verb `which` failed at FSReqWrap.oncomplete (fs.js:153:21) gyp verb `which` failed python { Error: not found: python gyp verb `which` failed at getNotFoundError (D:\0 - PROJETOS\teste7\node_modules\which\which.js:13:12) gyp verb `which` failed at F (D:\0 - PROJETOS\teste7\node_modules\which\which.js:68:19) gyp verb `which` failed at E (D:\0 - PROJETOS\teste7\node_modules\which\which.js:80:29) gyp verb `which` failed at D:\0 - PROJETOS\teste7\node_modules\which\which.js:89:16 gyp verb `which` failed at D:\0 - PROJETOS\teste7\node_modules\isexe\index.js:42:5 gyp verb `which` failed at D:\0 - PROJETOS\teste7\node_modules\isexe\windows.js:36:5 gyp verb `which` failed at FSReqWrap.oncomplete (fs.js:153:21) gyp verb `which` failed stack: gyp verb `which` failed 'Error: not found: python\n at getNotFoundError (D:\\0 - PROJETOS\\teste7\\node_modules\\which\\which.js:13:12)\n at F (D:\\0 - PROJETOS\\teste7\\node_modules\\which\\which.js:68:19)\n at E (D:\\0 - PROJETOS\\teste7\\node_modules\\which\\which.js:80:29)\n at D:\\0 - PROJETOS\\teste7\\node_modules\\which\\which.js:89:16\n at D:\\0 - PROJETOS\\teste7\\node_modules\\isexe\\index.js:42:5\n at D:\\0 - PROJETOS\\teste7\\node_modules\\isexe\\windows.js:36:5\n at FSReqWrap.oncomplete (fs.js:153:21)', gyp verb `which` failed code: 'ENOENT' } gyp verb could not find "python". checking python launcher gyp verb could not find "python". guessing location gyp verb ensuring that file exists: C:\Python27\python.exe gyp ERR! configure error gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable. gyp ERR! stack at PythonFinder.failNoPython (D:\0 - PROJETOS\teste7\node_modules\node-gyp\lib\configure.js:484:19) gyp ERR! stack at PythonFinder.<anonymous> (D:\0 - PROJETOS\teste7\node_modules\node-gyp\lib\configure.js:509:16) gyp ERR! stack at D:\0 - PROJETOS\teste7\node_modules\graceful-fs\polyfills.js:282:31 gyp ERR! stack at FSReqWrap.oncomplete (fs.js:153:21) gyp ERR! System Windows_NT 10.0.17134 gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "D:\\0 - PROJETOS\\teste7\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library=" gyp ERR! cwd D:\0 - PROJETOS\teste7\node_modules\node-sass gyp ERR! node -v v10.16.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok Build failed with error code: 1 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! node-sass@4.5.3 postinstall: `node scripts/build.js` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the node-sass@4.5.3 postinstall script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\Rodrigo\AppData\Roaming\npm-cache\_logs\2019-06-24T18_52_05_279Z-debug.log
Posts: 1
Participants: 1
@aclelland-netfore wrote:
Hey,
just tried to run a build today and ran into this issue. I initially didn’t do any updates or anything, just tried to run a build.
C:\Users*****.gradle\caches\transforms-1\files-1.1\appcompat-v7-26.1.0.aar\1f8a271632158355256c8b823247a330\res\values\values.xml:246:5-69: AAPT: error: resource android:attr/fontVariationSettings not found.
C:\Users*****.gradle\caches\transforms-1\files-1.1\appcompat-v7-26.1.0.aar\1f8a271632158355256c8b823247a330\res\values\values.xml:246:5-69: AAPT: error: resource android:attr/ttcIndex not found.
*****\platforms\android\app\build\intermediates\incremental\mergeDebugResources\merged.dir\values\values.xml:231: error: resource android:attr/fontVariationSettings not found.
*****\platforms\android\app\build\intermediates\incremental\mergeDebugResources\merged.dir\values\values.xml:231: error: resource android:attr/ttcIndex not found.
error: failed linking references.Failed to execute aapt
com.android.ide.common.process.ProcessException: Failed to execute aaptI’ve spent the past day looking around for ideas on what I’m supposed to do to fix it. I’ve tried updating cordova, updating some plugins, removing/cleaning the android platform and I can’t seem to figure out what exactly is causing the issue (I’ve been going between this error and a Merge error with appcompat and something called androidX).
From what I can gather fontVariationSettings was introduced in the android v28 API but I’m not too sure what exactly is happening or why this issue is happening now.
I have a feeling my environment in general is a little messed up now from updating/reverting things but this is what I’m at now:
ionic info:
cli packages: (C:\Users*****\AppData\Roaming\npm\node_modules)
@ionic/cli-utils : 1.19.2 ionic (Ionic CLI) : 3.20.0global packages:
cordova (Cordova CLI) : 7.1.0local packages:
@ionic/app-scripts : 3.1.9 Cordova Platforms : android 7.0.0 Ionic Framework : ionic-angular 3.9.2System:
Android SDK Tools : 26.1.1 Node : v8.9.4 npm : 5.6.0 OS : Windows 10Environment Variables:
ANDROID_HOME : C:\Users\*****\AppData\Local\Android\SdkMisc:
backend : proproject.properties:
target=android-26
android.library.reference.1=CordovaLib
android.library.reference.2=app
cordova.system.library.1=com.android.support:support-v4:24.1.1+
cordova.system.library.2=com.android.support:appcompat-v7:26.+
cordova.system.library.3=com.google.android.gms:play-services-analytics:+plugins:
cordova-plugin-camera 2.4.1 “Camera”
cordova-plugin-compat 1.2.0 “Compat”
cordova-plugin-datepicker 0.9.3 “DatePicker”
cordova-plugin-device 1.1.7 “Device”
cordova-plugin-file 6.0.1 “File”
cordova-plugin-file-opener2 2.0.19 “File Opener2”
cordova-plugin-file-transfer 1.7.1 “File Transfer”
cordova-plugin-filechooser 1.0.1 “File Chooser”
cordova-plugin-filepath 1.0.2 “FilePath”
cordova-plugin-geolocation 4.0.1 “Geolocation”
cordova-plugin-google-analytics 1.8.3 “Google Universal Analytics Plugin”
cordova-plugin-inappbrowser 1.7.2 “InAppBrowser”
cordova-plugin-ionic-webview 1.2.1 “cordova-plugin-ionic-webview”
cordova-plugin-ionic-wkkeyboard 1.1.15 “cordova-plugin-ionic-wkkeyboard”
cordova-plugin-network-information 1.3.4 “Network Information”
cordova-plugin-splashscreen 4.1.0 “Splashscreen”
cordova-plugin-statusbar 2.4.2 “StatusBar”
cordova-plugin-whitelist 1.3.3 “Whitelist”
cordova-sqlite-storage 2.3.1 “Cordova sqlite storage plugin”
Posts: 1
Participants: 1
@sitesbi wrote:
Hi,
we will use ionic 4 and appflow builds for our upcoming project - small conference app. I was wondering, what are the minimal requirements for ios and anroid (os version)?
Kind regards,
Jakub
Posts: 1
Participants: 1
@benyaminL wrote:
Hello. This problem related to Can't install debug apk
I just upgrade from Ionic 3 to ionic 5 and create new project, run and build the apk succesfully, but when I tried to install to my device, it’s not installed without any error. I don’t use androi studio, only android SDK, because my laptop just can’t hold android studio, too hog.This’s my environment
Ionic:
Ionic CLI : 5.1.0 (C:\Users\Ben\AppData\Roaming\npm\node_modules\ionic)
Ionic Framework : @ionic/angular 4.5.0
@angular-devkit/build-angular : 0.13.9
@angular-devkit/schematics : 7.3.9
@angular/cli : 7.3.9
@ionic/angular-toolkit : 1.5.1Cordova:
Cordova CLI : 8.1.2 (cordova-lib@8.1.1)
Cordova Platforms : android 7.1.4
Cordova Plugins : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 4.1.0, (and 4 other plugins)Utility:
cordova-res : 0.5.0
native-run : 0.2.6System:
(D:\Android\android-sdk).2.5
NodeJS : v10.15.1 (C:\Program Files\nodejs\node.exe)
npm : 6.4.1
OS : Windows 10My target SDK is 21 and the minimum is 19. Any suggestion?
Posts: 1
Participants: 1
@josh_sharpe wrote:
e2e tests seem to complete successfully though.
The last several lines below (the ones with “ERROR” in them) are triggered when I closed the open browser.
Shouldn’t tests work out of the box?
Comands run (and buried in output below):
- ionic start example blank --type=angular
- cd example/
- npm run e2e
- npm run test
Last login: Sun Jun 23 21:02:40 on ttys007 bash_profile bashrc ssh-agent count: 1 (11:05 AM) jsharpe@mbp:~ ionic start example blank --type=angular ✔ Preparing directory ./example - done! ✔ Downloading and extracting blank starter - done! Installing dependencies may take several minutes. ────────────────────────────────────────────────────────────────────────────── Ionic Advisory, tailored solutions and expert services by Ionic Go to market faster 🏆 Real-time troubleshooting and guidance 💁 Custom training, best practices, code and architecture reviews 🔎 Customized strategies for every phase of the development lifecycle 🔮 👉 https://ion.link/advisory 👈 ────────────────────────────────────────────────────────────────────────────── > npm i > fsevents@1.2.9 install /Users/jsharpe/example/node_modules/fsevents > node install node-pre-gyp WARN Using request for node-pre-gyp https download [fsevents] Success: "/Users/jsharpe/example/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" is installed via remote > node-sass@4.12.0 install /Users/jsharpe/example/node_modules/node-sass > node scripts/install.js Cached binary found at /Users/jsharpe/.npm/node-sass/4.12.0/darwin-x64-64_binding.node > core-js@2.6.9 postinstall /Users/jsharpe/example/node_modules/core-js > node scripts/postinstall || echo "ignore" Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library! The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: > https://opencollective.com/core-js > https://www.patreon.com/zloirock Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -) > node-sass@4.12.0 postinstall /Users/jsharpe/example/node_modules/node-sass > node scripts/build.js Binary found at /Users/jsharpe/example/node_modules/node-sass/vendor/darwin-x64-64/binding.node Testing binary Binary is fine npm notice created a lockfile as package-lock.json. You should commit this file. added 1186 packages from 1060 contributors and audited 54007 packages in 69.201s found 0 vulnerabilities > git init Initialized empty Git repository in /Users/jsharpe/example/.git/ > git add -A > git commit -m "Initial commit" --no-gpg-sign [master (root-commit) e7e3d25] Initial commit 37 files changed, 11769 insertions(+) create mode 100644 .gitignore create mode 100644 angular.json create mode 100644 e2e/protractor.conf.js create mode 100644 e2e/src/app.e2e-spec.ts create mode 100644 e2e/src/app.po.ts create mode 100644 e2e/tsconfig.e2e.json create mode 100644 ionic.config.json create mode 100644 package-lock.json create mode 100644 package.json create mode 100644 src/app/app-routing.module.ts create mode 100644 src/app/app.component.html create mode 100644 src/app/app.component.spec.ts create mode 100644 src/app/app.component.ts create mode 100644 src/app/app.module.ts create mode 100644 src/app/app.scss create mode 100644 src/app/home/home.module.ts create mode 100644 src/app/home/home.page.html create mode 100644 src/app/home/home.page.scss create mode 100644 src/app/home/home.page.spec.ts create mode 100644 src/app/home/home.page.ts create mode 100644 src/assets/icon/favicon.png create mode 100644 src/assets/shapes.svg create mode 100644 src/environments/environment.prod.ts create mode 100644 src/environments/environment.ts create mode 100644 src/global.scss create mode 100644 src/index.html create mode 100644 src/karma.conf.js create mode 100644 src/main.ts create mode 100644 src/polyfills.ts create mode 100644 src/test.ts create mode 100644 src/theme/variables.scss create mode 100644 src/tsconfig.app.json create mode 100644 src/tsconfig.spec.json create mode 100644 src/tslint.json create mode 100644 src/zone-flags.ts create mode 100644 tsconfig.json create mode 100644 tslint.json [INFO] Next Steps: - Go to your newly created project: cd ./example - Run ionic serve within the app directory to see your app - Build features and components: https://ion.link/scaffolding-docs - Get Ionic DevApp for easy device testing: https://ion.link/devapp ╭─────────────────────────────────────╮ │ │ │ Update available 5.0.1 → 5.1.0 │ │ Run npm i -g ionic to update │ │ │ ╰─────────────────────────────────────╯ (11:06 AM) jsharpe@mbp:~ cd example/ (11:08 AM) jsharpe@mbp:~/example (master) npm run e2e > example@0.0.1 e2e /Users/jsharpe/example > ng e2e ** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ ** Date: 2019-06-25T03:08:44.998Z Hash: 18b249165d6877193ff3 Time: 21425ms chunk {0} 0.js, 0.js.map () 16.4 kB [rendered] chunk {1} 1.js, 1.js.map () 12.9 kB [rendered] chunk {2} 2.js, 2.js.map () 17.3 kB [rendered] chunk {3} 3.js, 3.js.map () 5.48 kB [rendered] chunk {4} 4.js, 4.js.map () 1.4 kB [rendered] chunk {5} 5.js, 5.js.map () 1.45 kB [rendered] chunk {6} 6.js, 6.js.map () 3.22 kB [rendered] chunk {7} 7.js, 7.js.map () 1000 bytes [rendered] chunk {8} 8.js, 8.js.map () 1.73 kB [rendered] chunk {9} 9.js, 9.js.map () 93.8 kB [rendered] chunk {10} 10.js, 10.js.map () 31.4 kB [rendered] chunk {11} 11.js, 11.js.map () 33 kB [rendered] chunk {12} 12.js, 12.js.map () 25.7 kB [rendered] chunk {13} 13.js, 13.js.map () 26.6 kB [rendered] chunk {14} 14.js, 14.js.map () 24.7 kB [rendered] chunk {15} 15.js, 15.js.map () 26.1 kB [rendered] chunk {16} 16.js, 16.js.map () 23.9 kB [rendered] chunk {17} 17.js, 17.js.map () 23.9 kB [rendered] chunk {18} 18.js, 18.js.map () 32.5 kB [rendered] chunk {19} 19.js, 19.js.map () 33.6 kB [rendered] chunk {20} 20.js, 20.js.map () 33.7 kB [rendered] chunk {21} 21.js, 21.js.map () 34.2 kB [rendered] chunk {22} 22.js, 22.js.map () 30 kB [rendered] chunk {23} 23.js, 23.js.map () 31.1 kB [rendered] chunk {24} 24.js, 24.js.map () 31.5 kB [rendered] chunk {25} 25.js, 25.js.map () 32 kB [rendered] chunk {26} 26.js, 26.js.map () 30.4 kB [rendered] chunk {27} 27.js, 27.js.map () 30.4 kB [rendered] chunk {28} 28.js, 28.js.map () 23.6 kB [rendered] chunk {29} 29.js, 29.js.map () 24.4 kB [rendered] chunk {30} 30.js, 30.js.map () 23.4 kB [rendered] chunk {31} 31.js, 31.js.map () 24.2 kB [rendered] chunk {32} 32.js, 32.js.map () 25.5 kB [rendered] chunk {33} 33.js, 33.js.map () 25.6 kB [rendered] chunk {34} 34.js, 34.js.map () 25.6 kB [rendered] chunk {35} 35.js, 35.js.map () 25.7 kB [rendered] chunk {36} 36.js, 36.js.map () 23.9 kB [rendered] chunk {37} 37.js, 37.js.map () 23.9 kB [rendered] chunk {38} 38.js, 38.js.map () 42.3 kB [rendered] chunk {39} 39.js, 39.js.map () 43.2 kB [rendered] chunk {40} 40.js, 40.js.map () 21.3 kB [rendered] chunk {41} 41.js, 41.js.map () 21.9 kB [rendered] chunk {42} 42.js, 42.js.map () 25.7 kB [rendered] chunk {43} 43.js, 43.js.map () 26.6 kB [rendered] chunk {44} 44.js, 44.js.map () 33.6 kB [rendered] chunk {45} 45.js, 45.js.map () 34 kB [rendered] chunk {46} 46.js, 46.js.map () 32.8 kB [rendered] chunk {47} 47.js, 47.js.map () 32.8 kB [rendered] chunk {48} 48.js, 48.js.map () 21.4 kB [rendered] chunk {49} 49.js, 49.js.map () 22 kB [rendered] chunk {50} 50.js, 50.js.map () 31.6 kB [rendered] chunk {51} 51.js, 51.js.map () 32.1 kB [rendered] chunk {52} 52.js, 52.js.map () 32.4 kB [rendered] chunk {53} 53.js, 53.js.map () 33.5 kB [rendered] chunk {54} 54.js, 54.js.map () 42.5 kB [rendered] chunk {55} 55.js, 55.js.map () 43.3 kB [rendered] chunk {56} 56.js, 56.js.map () 24.1 kB [rendered] chunk {57} 57.js, 57.js.map () 25 kB [rendered] chunk {58} 58.js, 58.js.map () 33.5 kB [rendered] chunk {59} 59.js, 59.js.map () 33.5 kB [rendered] chunk {60} 60.js, 60.js.map () 22.8 kB [rendered] chunk {61} 61.js, 61.js.map () 22.8 kB [rendered] chunk {62} 62.js, 62.js.map () 46.5 kB [rendered] chunk {63} 63.js, 63.js.map () 46.5 kB [rendered] chunk {64} 64.js, 64.js.map () 15.9 kB [rendered] chunk {65} 65.js, 65.js.map () 16.1 kB [rendered] chunk {66} 66.js, 66.js.map () 22.8 kB [rendered] chunk {67} 67.js, 67.js.map () 23.1 kB [rendered] chunk {68} 68.js, 68.js.map () 22.4 kB [rendered] chunk {69} 69.js, 69.js.map () 22.7 kB [rendered] chunk {70} 70.js, 70.js.map () 25.4 kB [rendered] chunk {71} 71.js, 71.js.map () 27.2 kB [rendered] chunk {72} 72.js, 72.js.map () 25.8 kB [rendered] chunk {73} 73.js, 73.js.map () 27.3 kB [rendered] chunk {74} 74.js, 74.js.map () 16.6 kB [rendered] chunk {75} 75.js, 75.js.map () 16.9 kB [rendered] chunk {76} 76.js, 76.js.map () 16.6 kB [rendered] chunk {77} 77.js, 77.js.map () 16.9 kB [rendered] chunk {78} 78.js, 78.js.map () 16 kB [rendered] chunk {79} 79.js, 79.js.map () 16.1 kB [rendered] chunk {80} 80.js, 80.js.map () 17.6 kB [rendered] chunk {81} 81.js, 81.js.map () 18 kB [rendered] chunk {82} 82.js, 82.js.map () 24.9 kB [rendered] chunk {83} 83.js, 83.js.map () 27.8 kB [rendered] chunk {84} 84.js, 84.js.map () 26.9 kB [rendered] chunk {85} 85.js, 85.js.map () 28.8 kB [rendered] chunk {86} 86.js, 86.js.map () 25.2 kB [rendered] chunk {87} 87.js, 87.js.map () 28 kB [rendered] chunk {88} 88.js, 88.js.map () 22.2 kB [rendered] chunk {89} 89.js, 89.js.map () 22.3 kB [rendered] chunk {90} 90.js, 90.js.map () 49.9 kB [rendered] chunk {91} 91.js, 91.js.map () 52.4 kB [rendered] chunk {92} 92.js, 92.js.map () 46.3 kB [rendered] chunk {93} 93.js, 93.js.map () 48.4 kB [rendered] chunk {94} 94.js, 94.js.map () 12.9 kB [rendered] chunk {95} 95.js, 95.js.map () 13 kB [rendered] chunk {96} 96.js, 96.js.map () 26.6 kB [rendered] chunk {97} 97.js, 97.js.map () 28.2 kB [rendered] chunk {98} 98.js, 98.js.map () 46.5 kB [rendered] chunk {99} 99.js, 99.js.map () 46.5 kB [rendered] chunk {100} 100.js, 100.js.map () 29.9 kB [rendered] chunk {101} 101.js, 101.js.map () 30 kB [rendered] chunk {102} 102.js, 102.js.map () 16.6 kB [rendered] chunk {103} 103.js, 103.js.map () 16.6 kB [rendered] chunk {104} 104.js, 104.js.map () 6.43 kB [rendered] chunk {105} 105.js, 105.js.map () 6.5 kB [rendered] chunk {106} 106.js, 106.js.map () 17.5 kB [rendered] chunk {107} 107.js, 107.js.map () 17.6 kB [rendered] chunk {108} 108.js, 108.js.map () 6.43 kB [rendered] chunk {109} 109.js, 109.js.map () 6.51 kB [rendered] chunk {110} 110.js, 110.js.map () 44 kB [rendered] chunk {111} 111.js, 111.js.map () 44.5 kB [rendered] chunk {112} 112.js, 112.js.map () 44.4 kB [rendered] chunk {113} 113.js, 113.js.map () 44.8 kB [rendered] chunk {114} 114.js, 114.js.map () 19.8 kB [rendered] chunk {115} 115.js, 115.js.map () 19.8 kB [rendered] chunk {116} 116.js, 116.js.map () 16.6 kB [rendered] chunk {117} 117.js, 117.js.map () 16.6 kB [rendered] chunk {118} 118.js, 118.js.map () 19.4 kB [rendered] chunk {119} 119.js, 119.js.map () 19.4 kB [rendered] chunk {120} 120.js, 120.js.map () 17.5 kB [rendered] chunk {121} 121.js, 121.js.map () 17.6 kB [rendered] chunk {122} 122.js, 122.js.map () 17.8 kB [rendered] chunk {123} 123.js, 123.js.map () 17.9 kB [rendered] chunk {124} 124.js, 124.js.map () 13.7 kB [rendered] chunk {125} 125.js, 125.js.map () 13.8 kB [rendered] chunk {126} 126.js, 126.js.map () 19.4 kB [rendered] chunk {127} 127.js, 127.js.map () 19.4 kB [rendered] chunk {128} 128.js, 128.js.map () 10.4 kB [rendered] chunk {129} 129.js, 129.js.map () 10.4 kB [rendered] chunk {130} 130.js, 130.js.map () 27.4 kB [rendered] chunk {131} 131.js, 131.js.map () 28.1 kB [rendered] chunk {132} 132.js, 132.js.map () 10.8 kB [rendered] chunk {133} 133.js, 133.js.map () 10.8 kB [rendered] chunk {134} 134.js, 134.js.map () 17.3 kB [rendered] chunk {135} 135.js, 135.js.map () 17.3 kB [rendered] chunk {136} 136.js, 136.js.map () 4.24 kB [rendered] chunk {137} 137.js, 137.js.map () 1.6 kB [rendered] chunk {138} 138.js, 138.js.map () 24.5 kB [rendered] chunk {139} 139.js, 139.js.map () 24.5 kB [rendered] chunk {140} 140.js, 140.js.map () 2.83 kB [rendered] chunk {141} 141.js, 141.js.map () 2.88 kB [rendered] chunk {142} 142.js, 142.js.map () 4.43 kB [rendered] chunk {143} 143.js, 143.js.map () 4.45 kB [rendered] chunk {144} 144.js, 144.js.map () 10.7 kB [rendered] chunk {145} 145.js, 145.js.map () 10.8 kB [rendered] chunk {146} 146.js, 146.js.map () 4.44 kB [rendered] chunk {147} 147.js, 147.js.map () 4.45 kB [rendered] chunk {148} 148.js, 148.js.map () 10.1 kB [rendered] chunk {149} 149.js, 149.js.map () 10.2 kB [rendered] chunk {150} 150.js, 150.js.map () 13 kB [rendered] chunk {151} 151.js, 151.js.map () 13 kB [rendered] chunk {152} 152.js, 152.js.map () 27.6 kB [rendered] chunk {153} 153.js, 153.js.map () 28.4 kB [rendered] chunk {154} 154.js, 154.js.map () 14.3 kB [rendered] chunk {155} 155.js, 155.js.map () 14.5 kB [rendered] chunk {156} 156.js, 156.js.map () 14.4 kB [rendered] chunk {157} 157.js, 157.js.map () 15.1 kB [rendered] chunk {158} 158.js, 158.js.map () 14.4 kB [rendered] chunk {159} 159.js, 159.js.map () 14.4 kB [rendered] chunk {160} 160.js, 160.js.map () 24.4 kB [rendered] chunk {161} 161.js, 161.js.map () 24.5 kB [rendered] chunk {162} 162.js, 162.js.map () 15.1 kB [rendered] chunk {163} 163.js, 163.js.map () 15.8 kB [rendered] chunk {164} 164.js, 164.js.map () 13.6 kB [rendered] chunk {165} 165.js, 165.js.map () 13.6 kB [rendered] chunk {166} 166.js, 166.js.map () 3.08 kB [rendered] chunk {167} 167.js, 167.js.map () 12 kB [rendered] chunk {168} 168.js, 168.js.map () 14.6 kB [rendered] chunk {169} 169.js, 169.js.map () 7.92 kB [rendered] chunk {170} 170.js, 170.js.map () 1.63 kB [rendered] chunk {171} 171.js, 171.js.map () 1.36 kB [rendered] chunk {172} 172.js, 172.js.map () 5.03 kB [rendered] chunk {common} common.js, common.js.map (common) 20.2 kB [rendered] chunk {es2015-polyfills} es2015-polyfills.js, es2015-polyfills.js.map (es2015-polyfills) 285 kB [initial] [rendered] chunk {home-home-module} home-home-module.js, home-home-module.js.map (home-home-module) 4.92 kB [rendered] chunk {main} main.js, main.js.map (main) 31.8 kB [initial] [rendered] chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 237 kB [initial] [rendered] chunk {runtime} runtime.js, runtime.js.map (runtime) 8.79 kB [entry] [rendered] chunk {styles} styles.js, styles.js.map (styles) 88.6 kB [initial] [rendered] chunk {vendor} vendor.js, vendor.js.map (vendor) 4.37 MB [initial] [rendered] [11:08:45] I/file_manager - creating folder /Users/jsharpe/example/node_modules/protractor/node_modules/webdriver-manager/selenium [11:08:45] I/config_source - curl -o/Users/jsharpe/example/node_modules/protractor/node_modules/webdriver-manager/selenium/chrome-response.xml https://chromedriver.storage.googleapis.com/ ℹ ｢wdm｣: Compiled successfully. [11:08:46] I/downloader - curl -o/Users/jsharpe/example/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_75.0.3770.8.zip https://chromedriver.storage.googleapis.com/75.0.3770.90/chromedriver_mac64.zip [11:09:24] I/update - chromedriver: unzipping chromedriver_75.0.3770.8.zip [11:09:24] I/update - chromedriver: setting permissions to 0755 for /Users/jsharpe/example/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_75.0.3770.8 [11:09:25] I/launcher - Running 1 instances of WebDriver [11:09:25] I/direct - Using ChromeDriver directly... Jasmine started new App ✓ should be blank Executed 1 of 1 spec SUCCESS in 1 sec. [11:09:31] I/launcher - 0 instance(s) of WebDriver still running [11:09:31] I/launcher - chrome #01 passed (11:09 AM) jsharpe@mbp:~/example (master) npm run test > example@0.0.1 test /Users/jsharpe/example > ng test 11% building 10/10 modules 0 active25 06 2019 11:09:52.062:WARN [karma]: No captured browser, open http://localhost:9876/ 25 06 2019 11:09:52.067:INFO [karma-server]: Karma v4.1.0 server started at http://0.0.0.0:9876/ 25 06 2019 11:09:52.068:INFO [launcher]: Launching browsers Chrome with concurrency unlimited 25 06 2019 11:09:52.076:INFO [launcher]: Starting browser Chrome 25 06 2019 11:10:04.020:WARN [karma]: No captured browser, open http://localhost:9876/ 25 06 2019 11:10:04.097:INFO [Chrome 75.0.3770 (Mac OS X 10.14.5)]: Connected on socket BipkEtr2a4B4pZOPAAAA with id 89215906 Chrome 75.0.3770 (Mac OS X 10.14.5): Executed 3 of 3 SUCCESS (0.239 secs / 0.176 secs) TOTAL: 3 SUCCESS TOTAL: 3 SUCCESS Chrome 75.0.3770 (Mac OS X 10.14.5) ERROR DisconnectedClient disconnected from CONNECTED state (transport error) Chrome 75.0.3770 (Mac OS X 10.14.5): Executed 3 of 3 SUCCESS (0.239 secs / 0.176 secs) Chrome 75.0.3770 (Mac OS X 10.14.5) ERROR DisconnectedClient disconnected from CONNECTED state (transport error)
Posts: 1
Participants: 1
@PerfectCamp wrote:
I’ve been using jQuery Mobile (jQM) for about 10 years and am finally considering moving over to Ionic v4 and had a quick question…
I have been reading the docs on v4 and wanted to know if it was possible to have two html pages (page1.html and page2.html and link between them using the vanilla JS web components method. (ion-router, ion-nav)
In jQM we normally put html/body tags on every page which allowed users to link to any page directly in their browser. How does it work in Ionic v4? What would page1 and page2 look like? Should I include html, js and css links on every page like this? what about the ion-router stuff? What page and how can I get a transition from page1 to page 2? Thanks for taking the time to answer such a beginner question… I could not see any examples of ion-nav in the docs.
page1.html
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <meta name="viewport" content="initial-scale=1, maximum-scale=1, user-scalable=no, width=device-width" /> <title>Ionic Test Page</title> <script src="https://unpkg.com/@ionic/core@latest/dist/ionic.js"></script> <link href="https://unpkg.com/@ionic/core@latest/css/ionic.bundle.css" rel="stylesheet"> </head> <body> <ion-router use-hash="false"> <ion-route url="/page2.html" component="page2"></ion-route> </ion-router> <ion-app> <ion-header>Page 1</ion-header> <ion-content padding> <a href="page2.html">Go to Page 2</a> </ion-content> </ion-app> </body> </html>page2.html
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <meta name="viewport" content="initial-scale=1, maximum-scale=1, user-scalable=no, width=device-width" /> <title>Ionic Test Page</title> <script src="https://unpkg.com/@ionic/core@latest/dist/ionic.js"></script> <link href="https://unpkg.com/@ionic/core@latest/css/ionic.bundle.css" rel="stylesheet"> </head> <body> <ion-app> <ion-header>Page 2</ion-header> <ion-content padding> <a href="page1.html">Go to Page 1</a> </ion-content> </ion-app> </body> </html>The web app I want to build has 1000’s of dynamic data driven pages that I want to be able to load each page from the server. Is there a way to do this in Ionic v4 using vanilla JS methods?
Posts: 1
Participants: 1
@elduderino15 wrote:
I am not sure where to put the push notification logic in my app.
I have it working in theapp.component.tsnow and it properly registers and receives the push id.const pushObject: PushObject = this._push.init(new PushTools().parameters); console.log(JSON.stringify(pushObject)); pushObject.on('notification').subscribe((notification: any) => console.log('Received a notification', notification)); pushObject.on('registration').subscribe((registration: any) => console.log('Device registered', JSON.stringify(registration))); pushObject.on('error').subscribe(error => console.error('Error with Push plugin', JSON.stringify(error)));However, I am not sure when/ where / how to handle the
on(notification)call. Depending on the type of notification a specific app iew should be opened. Should I rather put the notification into my main view and forward to the sub-views from there, i.e. implementon(notification)in my main view than inapp.component.ts?It works, but I wish the documentation was bit better and the workflow how a proper production state app should work.
Is there a good example how this can be implemented?Thanks,
EL
Posts: 1
Participants: 1
@morphist wrote:
Hey all, was a bit of a journey to migrate, but glad I did it.
Here is a small article re the approach and some of the learnings:
https://medium.com/@sergey.rudenko/ionic-3-to-ionic-4-migration-gotchas-928174b5eb12
Posts: 1
Participants: 1
@adriansaenznovabase wrote:
Hi,
I’m using cocoapods to install plugin dependencies, but when i try to build the following error is displayed:I’m using cordova-ios 5.0.1. Any suggestion?
Posts: 1
Participants: 1
@josh_sharpe wrote:
This guide here: https://ionicframework.com/docs/building/ios
I’ve run into two issues almost immediately. I would submit a PR to update the guide, but honestly, I’m not sure what the best/correct approach is to solve these things:
- For me,
ionic capacitor add iosfailed with:[error] cocoapods is not installed. For information: https://guides.cocoapods.org/using/getting-started.html#installationAs I’m somewhat familiar with ruby, and already have
rvmsetup, I quickly added a.ruby-version,.ruby-gemsetandGemfileand gotcocoapodsinstalled easily enough. Not sure if that’s the preferred approach for the ios/capacitor community though.
- Once #1 was resolved, the same command failed with:
[error] Capacitor could not find the web assets directory "/Users/jsharpe/yellowstone/mobile_v5/www". Please create it, and make sure it has an index.html file. You can change the path of this directory in capacitor.config.json. More info: https://capacitor.ionicframework.com/docs/basics/configuring-your-appThis, I’m less sure about, but seems to indicate that my app hasn’t been built yet. Why is that required to install capacitor? Should something be added to this guide to clarify what steps should be taken?
For me, I ran
ionic buildwhich createdwww/index.htmland then capacitor add finished successfully. Is it required to build the project first? Should a note say something about that?
Posts: 1
Participants: 1
@ninecmoi wrote:
Hi,
i’m trying to set default value Or placholder in alertCtrl ? Is it possible ?
this code is not working :
let today = new Date().toLocaleDateString(); .... inputs: [ .... { name: "date", type: "date", value: today, placeholder: today },Thanks,
n
Posts: 1
Participants: 1
@Ganeshpatil25 wrote:
getting an issue while creating a build in ionic 3 . before two days were working fine with the code but got update that 4.1 version is not support please update to 4.6 minimum support version is 4.6.
Posts: 1
Participants: 1
@josh_sharpe wrote:
The capacitor ios guide has commands for cordova and capacitor all the way down to “Running with the Ionic CLI” where there is just a cordova command.
How do we launch a live-reload server with capacitor?
Posts: 1
Participants: 1
