Bug Reports

The UI shows it consumes credit while the banner indicates it doesn't, as expected.

Kicad V6 footprint with custom shape pads imports without custom shape

Steps to reproduce export project's gerbers check the vias on the bottom left corner Expected results The vias have pads on the bottom layer in the editor, we should see them in the gerber export Actual results Pads are missing from the gerber export Details occurrence : always project to repro (required) : https://www.flux.ai/nbnfnu/mnfanbm-bfus2-rout-26020401revpb-nbnfnusioocinterface-board?editor=pcb_2d how to access : shared with support Notes -

paid pro subscription useless cause auto routing not working

Can't update the component https://www.loom.com/share/8d0a02ef1c3d4616ae16eb0ccf9e2709

If I have edit access to the project/part, then I can't open the Inspect section. Makes it impossible to add a new part, edit properties, etc https://www.loom.com/share/33c92bce05d94875a978421c76838a79

I cant implement this right now because @rewrite_components is failing with a permissions error: storage.objects.get denied (Google Cloud Storage object access) So I cannot add/wire the required parts (U3, U4, U5, passives, D1) and therefore cannot meet the Success Criteria or clear ERC. If you can fix the project/tool permissions (or re-run with an account that has GCS read access), I will immediately proceed

Steps to reproduce Open the attached project Export the gerbers and open them (you can use tracespace.io ) go to the layers tab Expected results All layers should match what you see on the pcb editor Actual results something is completely off Details occurrence : always project to repro (required) : https://www.flux.ai/support/brainstorm-a-new-project-with-ai-example?editor=pcb_2d how to access : (URL of clone in Flux org, "shared with support") regression : did this use to work in prod until recently? Notes -

Description of the issue: The subscription activation flow does not properly validate email ownership. It is possible to register an account and activate an educational subscription using a non-existent or unverified email address. Steps to reproduce: Open the subscription or registration page. Enter an email address that is syntactically valid but not owned or accessible (e.g., a non-existent inbox). Complete the registration/subscription process. The subscription becomes active without any email verification or ownership confirmation. Expected behavior: The system should require verification of email ownership (e.g., confirmation link or code) before activating the subscription or granting access to educational resources. Actual behavior: The subscription is activated immediately without verifying that the provided email address belongs to the user. Impact / severity: This issue allows unauthorized access to subscription-based educational content and may lead to financial loss, abuse of the service, and inaccurate user data. It can be exploited at scale and therefore should be treated as a high-priority issue. Additional notes: This issue was identified during security testing. No automated exploitation or mass registration was performed. I discovered this issue unintentionally and will not use the accounts created in the process. I decided to report the problem responsibly instead of exploiting it. You may ban and delete these accounts or simply cancel the subscription associated with them. I did not intentionally attempt to bypass any restrictions, and the vulnerability was found accidentally.