So I've been playing around on Magento 2 community and it looks like only allowing certain shipping destinations is not stopping others from being selected, and not warning the customer...
I Have child-themed, however it looks like even in the bundled themes this issue persists


It lets me checkout, but the checkout looks like this (could be separate issue)

I do have five store views, but I've only used the global config to setup shipping via the table shipping rates, which I have imported successfully.
While it's great being able to have multi-currency, multi-language, and a shipping table rate for setting per country / country + region, if it doesn't work in a way that is clear to the end user, then it could be a problem.
Can second this issue and add that "Allowed Countries" seems to not work also under Configuration -> General > Country Options



Why no one reply to this huge bug?
Hi @Lewiscowles1986 , @chris-brabender ,
thank you for reporting this issue and we are sorry for delay. This bug really exists on 2.0.7 version. But it is fixed on current develop branch. You can upgrade your code from develop branch or wait until next release.
Feel free to reopen this issue if you will have the same problem on next Magento version.
Thx @NadiyaS
I'm personally waiting for next release and hope to finally go live with my project.
We have the same bug in 2.0.7. At the checkout ALL countries are shown - not just the selected in then backend. Is there a way to fix this on 2.0.7 as this is a major bug not allowing anyone to go live with wrong shipping countries?
Will this be fixed in 2.1 or sooner? Is there any information when 2.1 is coming?
Thanks!
Hi @NadiyaS
My project running 2.0.7 also have this issue, could you let me know which files / folders need to be replaced?
I can find the fixed files / folders in current develop branch?
Thanks!
@perry3181 have you upgrade to 2.0.8?
Hi @perry3181 ,
if you do not want to do upgrade to 2.1 version you can upgrade your code to 2.0.8. It is the best way to fix this problem, and not to change files separately.
Hi @LucScu and @NadiyaS,
I not yet upgrade to 2.0.8. Actually, I want to upgrade to 2.1 few weeks ago, but not success. Due to the below error. Then I spent much time to restore the system to 2.0.7. So that I give up to upgrade to 2.1 until I find the solution.
Do you guys know if upgrade from 2.0.7 to 2.0.8 will have the same issue "Webapi does not exist"?
I remember that I upgraded 2 times, from 2.0.1 to 2.0.3, 2.0.3 to 2.0.7, the upgrade process is smooth and without error message in console log.
[2016-07-04 14:15:02 UTC] An error occurred while executing job "setup:upgrade {"command":"setup:upgrade"}": Could not complete setup:upgrade {"command":"setup:upgrade"} successfully: Class Magento\FrameworkApp\Cache\Type\Webapi does not exist
Hi @LucScu and @NadiyaS,
I just go to the system upgrade page, it still stick with the console log and can't be exit :(

there is an error like everywhere, you have to find how to fix it by yourself.
@perry3181 This issue has been closed as the original issue reported has been resolved. If you wish to report an upgrade issue please file a new issue and provide all steps to reproduce the error you are seeing.
Most helpful comment
Hi @perry3181 ,
if you do not want to do upgrade to 2.1 version you can upgrade your code to 2.0.8. It is the best way to fix this problem, and not to change files separately.