The issue occurs when editing an existing application by assigning a new API... the current plan of the newly added API shows as "Sandbox" even though that plan was removed and the only one available is Bronze.
When you save it... then go to "Edit" to view it... it does show correctly.
Just so you know that "Sandbox" is not there... the screen shot of the API Plans...
Any idea where the "Sandbox" is being referenced from?
I would be curious to see what .xml's you have referencing Account Plans. If you go into the CMS of portal and pull up this path:
/ sitebuilder/ content/ groups/ AccountPlans
How many .xmls do you see? If you open them up, do any reference sandbox?
In the account plans folder there is only 1 XML and it doesn't reference sandbox... BUT under the APIPlans folder there is also 1 XML file and it is called sandbox.xml.
The original sandbox plan was renamed within the portal to Bronze. The file name apparently doesn't get changed but the contents of the file doesn't reference sandbox.
I tried renaming the file but when I ran my test the new API's added to an existing application still showed "sandbox" until I saved it.
So it turns out that under /SYSTEM/template_resources/js/layer7... there is a file called "layer7.controls.js" which has "Sandbox" hard coded.
We were able to work around this by just moving the text from the tag. When adding an API to an application, the current plan would then appear as empty... then when saved it would show the available api plan.