Unexpected change in Carrier Service API behaviour

I noticed a recent change in the Carrier Service API. Before, creating a Carrier Service would automatically add it to all shipping profiles. Now, it only gets added to the default shipping profile, which impacts how merchants set up our app.

I couldn’t find anything about this in the changelog, and a few other developers have noticed the same thing (see Slack discussion here).

Could someone confirm if this was an intentional update, or if it’s an unexpected issue that might be fixed in the future? Thank you!

Hey @Patrick_Jakubik

Digging into this now - will let you know asap if this is a result of an update on our side.

Hey @Patrick_Jakubik

It doesn’t look like anything changed on our side related to how carrier services would be applied to shipping profiles.