havemaskwilltravel

I did all you said, which initially did not solve the issue. After a few hours the issue seemed to have resolved itself spontaneously. Is it possible that it took some time for the changes to take effect?

The upcoming update you referred to, is that SuperPWA 2.2.29 released on August 2nd?

I’ve recently submitted my web app to both the Play store and App store and the app has now been approved by both platforms, which is very nice.

The Play store did notify me of the following:
Your highest non-compliant target API level is Android 13 (API level 33). To ensure you can continue updating your app, do the following:

• Update your app to target Android 14 (API level 34) or higher.
• Publish a new version of your app in production. Before you do this, you can test your app with internal, closed, or open tests.

What would you recommend?

Had the exact same problem.

In Woocommerce I had set the decimal separator to a comma [ , ] and the minimum amount for free shipping to €82,64. Free shipping was shown when the cart total reached €82,64 or more but disappeared when it reached €100 or more.

I changed it to €82.64 (using a period instead of a comma) and the problem was solved. Why on earth does Woocommerce do this?

Thanks @femkesearacon

I have deactivated all plugins, then activated them again, and the JSON error did not occur anymore when updating or publishing the page. I have no idea why.

Hi Mushrit, I’ve done that to no avail.

Hey Maybellyne, thanks, I’ve updated both plugins to v22.8 but the problem remains. It looks like custom WP shortcode combined with Yoast is causing the JSON response: when I remove the shortcode from my homepage, the page is published with no error. I’ve tried and google to see if others have experienced this and this sounds very similar:
https://stackoverflow.com/questions/77383545/wp-shortcode-returns-json-error-despite-showing-content-on-website

I don’t know if it’s directly caused by your plugin(s) but when I deactivate Yoast SEO, I can publish the page with no error. When I activate Yoast SEO, I can ONLY publish my page with no JSON error if the custom WP shortcode I’ve mentioned, is removed first. The shortcode has nothing to do with Yoast, it’s just a search form.

• This reply was modified 6 months ago by havemaskwilltravel.
• This reply was modified 6 months ago by havemaskwilltravel.

Patiently waiting for that, thank you.

Apple reverses decision to kill home screen web apps in the EU

Apple has?announced?that it’s?reversing?its previously?announced decision?to no longer support home screen web apps, also known as Progressive Web Apps (PWA), on the iPhone. As of Friday, March 1, 2024, EU users will continue to be able to install and use home screen web apps on iOS going forward.?

https://mashable.com/article/apple-reverses-decision-home-screen-web-apps-pwa-eu

I have personally NOT tried to publish a PWA on the App store before, however, according to quite a few articles it is definitely possible using pwabuilder.com.

If your web app meets a few baseline PWA requirements, you can use PWABuilder to validate, score, and package your application for stores.

• Your PWA needs to be published at a public URL.
• It must have a complete?web app manifest.
• The app has to be served with HTTPS.

Source: https://web.dev/articles/pwas-in-app-stores

I recently experienced something similar. When I activated Yoast SEO free 22.4, I got a fatal error. In my case it turned out that file wp-seo-main.php was missing. When I downloaded a new copy of the plugin and installed it using FTP, the fatal error did not occur anymore.

Thank you.

“While EU users can still access Home Screen web apps, they will now do so within their browser window rather than as standalone apps, and certain functions like Push notifications may be unavailable.”

Does that also apply to PWAs built & published for the App store, using pwabuilder.com for example, and your Super PWA plugin? Would it be wise to wait for now before building & publishing a PWA through pwabuilder.com? What would you suggest?

Thank you for your reply. I found the problem. We had multiple product categories with the same name, with different slugs. Two or more prod cats with the same name will automatically get a different slug, however that slug isn’t visible everywhere. Various products had been assigned to the wrong product category (which had the correct name, but the wrong slug).

I’ve got the same issue here. Unless I deactivate Yoast SEO, Contact form 7 does not work and the spinner continues to be shown. This issue didn’t happen in the past AFAIK.

Thank you, will do.