Mobile Error // Unhandled Promise Rejection - can't read the WP REST API

dejangeorgiev · 7 September 2020 20:04

Hello team,

I am getting this error on Mobile, more specific on Safari on iPhone 11 Unhandled Promise Rejection: Error: Add the URL of your WordPress REST API in state.source.api. The thing is that this happens on mobile only, so i am a bit confused…

Repo: https://github.com/dejangeorgiev/ruthgeorgiev-frontity

Thank you very much for your help.
Best,
Dejan

David · 10 September 2020 07:34

Hey @dejangeorgiev! We were able to reproduce your problem and we are taking a look at it. As soon as we know something more we will let you know.

Thanks for your patience.

dejangeorgiev · 10 September 2020 08:55

Hey @David

Great. Looking forward for your feedback!

Thank you so much.

David · 10 September 2020 09:45

It seems to be a problem with the implementation we did to deprecate the URL constructor that we exported from frontity:

github.com

frontity/frontity/blob/2bdf7dbe44fec3b0c08aae7175bee76d47811a41/packages/frontity/src/utils/url.ts

/**
 * DEPRECATED.
 *
 * To be removed in the v2 version. Now that we've deprecated Node 8,
 * maintaining this is no longer required.
 *
 * It was meant to be used for compatibility with Node 8, where the global
 * `URL` was not present and therefore this was not possible without importing
 * URL from `"url"`.
 *
 * @example
 * ```js
 * const url = new URL("https://domain.com");
 * ```
 */

import { warn } from "@frontity/error";

/**
 * Re-export to add a deprecation warning.

This file has been truncated. show original

For some reason, it doesn’t work well in Safari (tested in version 13.1.2) and it throws an error, making the code to fail in the init() action of @frontity/wp-source and showing the error you mentioned.

I opened an issue in order to fix this (frontity/frontity#565). In the meantime, it should work fine using the previous version of frontity (1.10.1).

We’ll keep you posted!

EDIT: We already find a solution and we are going to publish a new version today! You can wait for the new version of frontity instead of installing the previous one

dejangeorgiev · 10 September 2020 10:32

Great job @David!
Thank you guys for your support!

Let me know when the new version is available.
Many thanks.

luisherranz · 10 September 2020 10:33

@David found the solution, so I’ve made a PR. It should be ready to merge as soon as he reviews it:

EDIT: Merged

SantosGuillamot · 10 September 2020 14:07

We have just released a new version with the fix. If you update the project following this guide, the problem should be solved. Let us know if you keep having that error.

dejangeorgiev · 10 September 2020 19:04

hey @David @luisherranz @SantosGuillamot & co,

Thank you guys for your support!
Just tested it - works perfectly!

lagerroos · 11 September 2020 06:58

Of course, this struck me right as I was making the first production release. The new fix solved this. Thank you guys for your hard and appreciated work! @luisherranz @SantosGuillamot and everyone else on the Frontity team.