Yes that is expected. In the release notes I explain how to fix this issue. There are 3 actions required to make sure everything works properly in v1.1.2. A few users did not look at the release notes in detail and missed the required actions. Next time some actions are required in an update I will look into adding a message in the unity editor when people import the package.
