Ionicons: latest ion-icons not working with ionic5 on uiwebview and wkwebview

I can also confirm this issue. In my case, the icons appear the first time but when I force close the Ionic app and open the app again, they disappear because the SVG does not load in the Shadow Content as shown in the screenshot by @rashmendis

Same for me
On Jun 15, 2020, 5:45 PM +0530, himanshuarya notifications@github.com, wrote:

I can also confirm this issue. In my case, the icons appear the first time but when I force close the Ionic app and open the app again, they disappear because the SVG does not load in the Shadow Content as shown in the screenshot by @rashmendis
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Another observation is that even on using a custom SVG, the SVG does not load the second time on force closing the app.

Yes. Same for me
On Jun 15, 2020, 6:21 PM +0530, himanshuarya notifications@github.com, wrote:

Another observation is that even on using a custom SVG, the SVG does not load the second time on force closing the app.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Same issues for me

Same here. Not only with UIWebview, also with WKWebview.

@rashmendis how did you used the old ionicon:4.6.3? Did you uninstall the 5.x and install the 4.x?

Tried that but since ionicon is a dependency for ionic it will install ionicon5 with ionic 5. So I had to downgrade ionic to ionic4
On Jul 19, 2020, 10:45 AM +0530, jdpsbh notifications@github.com, wrote:

@rashmendis how did you used the old ionicon:4.6.3? Did you uninstall the 5.x and install the 4.x?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@brandyscarney is anyone from the Ionic team looking into any of the ion-icon issues? It looks like none of the ion-icon issues haven't been assigned, triaged, or being investigated upon. This issue is one of the major issues in Ion-icon v5 which comes along bundled with Ionic 5. This is a blocker issue that is preventing us to upgrade from Ionic 4 to Ionic 5. Can you please get this issue resolved?

Hey @himanshuarya, we hear you. Can you share more information on the issue you're seeing (code sample, screenshots)?

@rashmendis Would you be able to share the code of the sample ionic app in which you were able to reproduce this issue?
@bensperry - @rashmendis had shared a DOM screenshot where there is no content in the icon-inner div in the Shadow Content. Please refer to that screenshot in the first comment.

@bensperry Just do a ionic start myApp tabs and create an app with ion-icons. Then have to build the app and run it inside a uiwebview or wkwebview in iPad or an Apple device.

Hey @rashmendis, this is frustrating. We are unable to reproduce the issue on our end.

Basically, we need more info. What are you using to deploy the app—are you using Capacitor or Cordova? Please share the exact steps for us to follow and be as specific as possible. This will greatly help us nail down exactly what might be going wrong more quickly.

@bensperry Not using both Capacitor or Cordova. What you have to do is create a tab app using ionic start myApp tabs. Then you need to build the app using ionic build --prod. Then You have to create a iOS app with a UIWebView or WKWebView and load the ionic app which we build earlier. App is working directly on iPad Safari app without any issues but not working inside the UIWebView or WKWebView. I was testing it inside a Commercial iOS app so won't be able to share the code. But as you can see in the comments it's a common issue when we run the ionic5 app inside a iOS WebView.

Thanks for the issue. So just using WKWebView or UIWebView is not going to be sufficient to get Ionicons loading. The reason is that when an icon SVG is loaded, it is treated as a local file, and WKWebView has some limitations referencing local files by itself.

The best solution here is to use a small local server to serve the files. The easiest way to do this is to use Capacitor. You can view our Getting Started Guide to quickly integrate Capacitor into your existing app.

Can you try your app with Capacitor and let me know if it resolves the issue?

I was facing same issue. my issue was solved by changing path in angular.json file
Old path:
....
"assets": [
{
"glob": "/",
"input": "src/assets",
"output": "assets"
},
{
"glob": "/.svg",
"input": "node_modules/ionicons/dist/ionicons/svg",
"output": "./svg"
}
],
....

new path:
....
"assets": [
{
"glob": "/",
"input": "src/assets",
"output": "assets"
},
{
"glob": "/.svg",
"input": "node_modules/ionicons/dist/svg",
"output": "./svg"
}
],
....