Just wanted to post an update, we had this live for a little bit Monday/Tuesday but rolled it back temporarily to fix some issues with the header. We will be implementing it again this week, please note that we have changed the header format to bypass-multi-location-support: true
Please note that we have removed the underscore (_) and changed it to a dash (-). It came to our attention that some technologies don't play as well with headers that contain underscores.
To clarify, do you plan to deprecate the current Inventory update method (without locations) for existing Private Apps?
The old way of using inventory is considered deprecated across the board. There isn't currently a date where we will block the old behaviour on Private apps, but we do consider it legacy and therefore will likely be a date in the future.
What would happen in situations where an installed Public App blocks the ability to turn on Inventory by Location?
This is already live. But I think you mean after the deadline? After the deadline we would be blocking those API calls from the Public apps therefore they are no longer blocking and it would be lifted.