Perhaps the new Angular build system? That was my problem, see this post maybe its the same thing?
Upgrade from Angular 14 to Angular 19 and Ionic6 to Ionic8
GitHub and SSH access not real clear with Ionic
What repo is being cloned directly from GitHub and where do you see this in the docs?
Conditionally import plugin
I have a custom plugin that allows me to connect to my hardware
the packaging has a bug, with IOS Appstore asking for a file I don’t have for a 3rd party lib…
anyhow, I can conditionally compile without that lib function…
BUT I cannot conditionally import the plugin
trying
if(useEstimote)
import { EstimotePlugin as EstimoteUWBPlugin } from 'estimoteplugin4';
else
const EstimotePlugin = ()=>{}
error
[vite:vue] [vue/compiler-sfc] 'import' and 'export' may only appear at the top level
any magic ???
Conditionally import plugin
Can’t you use a dynamic import? See import() - JavaScript | MDN.
GitHub and SSH access not real clear with Ionic
Hello,
So I started here:
Create your Ionic App
(I accepted the default icon, tab layout, and then selected Vue framework)
Logged in with my account (Didn’t like how it made me do a mid stream account create/log in, should have just allowed me to create the whole test app without breaking the flow).
So waited like 10 minutes while the website did it's thing and it seemed to go into a Deep Thought loop and never come back.
When I pressed F12 in chrome to bring up the debugger there was a sea of ionic/google javascript / html issues.
So I can’t take a screen capture of the webpage where it showed me how to pull the app that I created with the wizard down from the github account that I also had to link up midstream. Only the commands that Ionic sent to pull this newly created repo down … nope, the git clone http:// doesn’t work any longer because github disallows password http pulling. So then you were sent on another errand to go create a SSH access. When you do this, you have to use a new SSH url that’s quite different than the one that ionic provided.
If Ionic wanted to be excellent, on every page there should be a feed back button from those who try out their builder and give feedback and it could take all the screenshots of the page, logs etc for engineering and usability reviews. Better yet, would be to offer to guide / observe a few users via a live zoom video feed and get their knee-jerk reaction in real time to the system flow. If it doesn’t work right, then in no way is this system ready for prime time. Have all the engineers who worked on the Appflow watch and take notes.
GitHub and SSH access not real clear with Ionic
Ah, I see. I’ve never used that GUI/start page. I always use the CLI to start a new Ionic project There are way less hoops if you use the CLI.
Conditionally import plugin
thanks, wasnt aware of this. works
GitHub and SSH access not real clear with Ionic
It’s just real confidence-reducing that there is no continuous improvements, dedication to quality. Where are those Six Sigma bandits these days? Where is all that CI/CD regression testing and Q/A? You would think someone would be interested in keeping the main conduit for app generation tuned up better than a daily driver. Guess not.
Several years back, I had used Ionic to create some Test apps, all web driven, and it worked great. When they made the switch from Angular 2.0 to 3.0 or something like that, Ionic ditched the old-web interface, the old code was no longer compatible, there was no auto upgrader path. it was a total pump and dump situation. So I departed. I decided to give Ionic another go to see if the old ways were abandoned … nope. Seems more of the same. I can’t run a business on a technology that doesn’t have accountability or integrity. This stuff has got to be rock solid because I don’t want to be in the hot seat explaining to my customers that I chose poorly
Can’t say its much worse than Flutter or React Native, those are both abominations when it comes to a quick start guide that works all the way through as well.
All these guides have to be heavily stack overflow supplemented, “Oh you got to do this…then that” I mean how lazy can the developers get not to provide a few scripts here and there to run to facilitate the setup and then do a few system sanity checks to make sure the system is ready for prime time? If nothing else, list the prerequisites first and links to some guides to let the user know the scope of work ahead of time before getting half way through and then dropping a bomb on them. It’s appalling that the experts have left things like this. No one will adopt, it will just leave a bad taste in their mouth and they will move on to some other technology.
Error compiling in XCode 16.2
Hello everyone,
We have a Capacitor+Angular application and since we have updated the XCode version to 16.2 we are having problems compiling due to the Apple Swift version.
We have updated Capacitor versions to the latest 6.2.0 and the issue still appears. Also add that the project compilation works without problems, the error occurs when we try to compile from XCode with the Product>Build menu.
Before updating XCode to version 16.2 the app was working and building on iOS was fine. It started to fail today after updating XCode.
It seems to be due to some issue with the Swift version but we can’t find any information about it and the errors we get are not documented.
We are attaching some screenshots in case they can be of help in understanding the problem we are having.
Our system is running Swift version 6.0.3.
Thank you very much for your help.
All the best!
Ion-Searchbar Not Visible on Android Native Build but Works in Browser
Hi, sorry for the delay in responding and thank you for your comment.
It does seem like that’s the issue. It looks like the styles aren’t being imported correctly in the production build. How can I ensure that the required CSS is included properly in the final build?
Any suggestions would be greatly appreciated. Thanks!
Ion-Searchbar Not Visible on Android Native Build but Works in Browser
I’ve solved it by adding this in angular.json
:
"production": {
"buildOptimizer": false,
...
}
Error compiling in XCode 16.2
XCode 16.2 seems to still be in beta (source). Maybe Capacitor 6 doesn’t support that version You could try Capacitor 7 which is in beta or downgrade back to XCode 16.1.
Another possibility, the errors show x86_64 whereas the target is arm64. Maybe you have the wrong target selected? Or maybe this is a bug in 16.2 since it is still in beta.
Blank page after splash Ionic 7
Olá pessoal, sou novo no Ionic e estou com problemas para executar o aplicativo no Android. Minha versão do Ionic é 7, o aplicativo é simplesmente o projeto em branco com ngmodules.
NullInjectorError: R3InjectorError(Platform: core)[t -> Cr]
Overlapping with single ( + )
Hi everyone! I’ve been stuck on an Ionic + Vue 3 + Vite issue.
One ion-page
overlays another instead of transitioning away. The URL updates, but the old remains in the DOM with display: inline
. Only on a manual refresh of the url does the old page disappear.
Behavior: Navigating from “web-home” → “login” leaves both elements stacked. In DevTools, both show display: inline;. Refreshing removes the old page as expected.
Warning: [Ionic Warning]: The view for path /web-home does not have the required component… even though is clearly in WebHome.vue.
I have created a sample_project
to demonstrate the problem.
Repo: https://github.com/arpitpatel901/tlbot_frontend/tree/sample_project
Branch: sample_project
Setup:
Ionic 8.4.1
Single + in App.vue
Standard Vue Router from @ionic/vue-router
Each page has , but transitions still stack pages.
Does anyone know why might not be recognized, or how to avoid the “inline stacking” issue?
Blank page after splash Ionic 7
A blank page is usually due to a JS error usually caused by an unsupported JS feature in the WebView.
Run the app on your Android via Android Studio and check DevTools in Chrome to see if there are any errors. You can open DevTools for the device on your computer by going to chrome://inspect/#devices in Chrome.
Overlapping with single ( + )
What’s up with this:
router.afterEach(() => {
nextTick(() => {
document.querySelector('#main .ion-page.ion-page-invisible')
?.classList.remove('ion-page-invisible');
});
});
On a side note, you don’t typically want to use child routes (children
) unless using Ionic Tabs. You can review the docs here on this - Vue Navigation: Use Ionic + Vue Router to Create Multi-Page Apps.
Blank page after splash Ionic 7
I already tried it. There’s nothing on the console in the web browser.
Only the Android app has the issue.
Here’s the link to the project. Can you check where my mistake is?
Overlapping with single ( + )
@twestrick Thanks for looking into this !
Sorry, that was one of fix that worked for someone else here, so I tried that. But that problem seems to have been related to the older ionic versions, so I removed that piece of code, but no change.
Still having the issue.
I have looked at the page you mentioned. Ideally children routes should not cause the problem since the issue occurs before that [transitioning from WebHome->Login page]. I am trying to make sure I follow the ideal ionic principles - 1 Ion-App, 1 Ion-Router and each view having IonPage at the top layer.
Blank page after splash Ionic 7
Sorry, I don’t download random ZIP files. A GitHub repo would be preferred.