🎉 Welcome to the Mobify DevCenter, our new home for v2.0 documentation and developer resources! (For now, the site is desktop-only.) Switch to old site
close
Mobify DevCenter
DocumentationAPI & SDK ReferenceHow-To Guides
search_icon_focus

Salesforce Commerce Concepts: General Troubleshooting

Introduction

Note: The Salesforce Commerce Concepts series is designed to dive into some of the more challenging topics you may encounter when working with Salesforce B2C Commerce.

This lesson focuses on troubleshooting common issues that can arise while working with Salesforce B2C Commerce backend.

Essential prerequisites

To get the most out of this guide, make sure you:

  • If you’re not a backend developer yourself, you’ll need to make friends with one, as a lot of the tactics discussed in this guide require backend development expertise. Often, projects require changes to expose more data using requests to the Salesforce Commerce Cloud Open Commerce API, (OCAPI). The best case scenario is being able to work with a backend developer who understands the site’s OCAPI implementation. This will allow you to make changes to the site that will save you from having to scrape the data from desktop, or send multiple requests to get the same data.
  • Complete our initial Salesforce Connector setup steps.
  • Have Salesforce B2C Business Manager access for the development environment (not the production environment). This is very useful for debugging and testing certain kinds of issues, such as when the availability of a product changes.
  • Be able to access the Salesforce Documentation, so you can pause and review the underlying API when necessary.

Troubleshooting

In this section, we’ll go through the most common issues you may need to troubleshoot during a Mobify project with a Salesforce backend.

iOS and basic auth

Salesforce Commerce development environments are often protected using Basic HTTP authentication which uses the Authorization HTTP header. Unfortunately, OCAPI authentication using JWT also uses the Authorization HTTP header. The Safari browser cannot provide both Basic HTTP authentication and JWT authentication. The JWT authentication header is not correctly sent and OCAPI requests fail.

To test the PWA on Safari, disable basic authentication on your Salesforce Commerce environment. If the environment must be protected, use another method of access control like IP whitelisting instead.

PUT methods

OCAPI requests using the PUT method no longer work on staging or production environments. Instead, a POST method must be used with the x-dw-http-method-override header. Read more in the Salesforce Documentation, and in the Salesforce developer community.

Wrap up

After reading this guide, we hope you can troubleshoot some of the common issues we’ve seen during Mobify builds with Salesforce B2C Commerce.

After completing this guide, you may want to review some of the concepts, such as session bridging, or checkout that were introduced in the other guides in this series.