I’ve previously set my application’s app proxy via the partner dashboard but with the recent announcement that most (if not all) configs will be set via the toml, I’ve moved (and changed) my proxy configurations to the toml.
When looking at the settings in the partner dash, the proxy subpath is set correctly (deployed the changes to my dev app). However, when testing my application’s code (using the new proxy subpath), I’m returned a 404 page.
If I switch the subpath to the previous one, I’m able to get to the correct route.
This suggests that the subpath is being cached somewhere and the cache hasn’t been refreshed. I tested multiple times over a 24 hour time range and nothing has changed.
Yesterday, I looked through the community for explanations and there was one thread which its explanation made no sense; “store set proxy; proxy subpath no longer the one set by app“ (paraphrasing). I never set the subpath using my dev store.
Additional things I’ve tried:
- uninstalling/reinstalling
- changing the proxy subpath from the partner dash
- clearing browser cache
I’ll try to install on another store and see what happens.