The mobile app currently faces an issue where the Blaze card disappears upon app relaunch for users with Jetpack versions older than 12.0. This happens due to the absence of the can_blaze property in the sites/:id endpoint for these versions. While the property is present after the initial login via me/sites, it is missing in subsequent app startups when sites/:id is called, leading to the Blaze card being hidden.
Solution
After a thorough discussion and analysis pe5sF9-2Gh, the preferred solution is to display an error on the Blaze card or in the Blaze flow for users with an outdated Jetpack version (<12.0). This approach informs users of the need to update their Jetpack plugin to restore full functionality, including the visibility of the Blaze card.
Detect when a user's site is running on an outdated version of Jetpack (<12.0).
Display an informative error message on the Blaze card or in the Blaze flow, prompting the user to update their Jetpack plugin.
dangermattic
commented
4 weeks ago
The mobile app currently faces an issue where the Blaze card disappears upon app relaunch for users with Jetpack versions older than 12.0. This happens due to the absence of the
can_blazeproperty in thesites/:idendpoint for these versions. While the property is present after the initial login viame/sites, it is missing in subsequent app startups whensites/:idis called, leading to the Blaze card being hidden.Solution
After a thorough discussion and analysis pe5sF9-2Gh, the preferred solution is to display an error on the Blaze card or in the Blaze flow for users with an outdated Jetpack version (<12.0). This approach informs users of the need to update their Jetpack plugin to restore full functionality, including the visibility of the Blaze card.
iOS issue: https://github.com/woocommerce/woocommerce-ios/issues/12987