Skip to main content

Unable to edit custom Extension/Block due to Chrome changing security settings

  • December 13, 2024
  • 2 replies
  • 0 views

When editing a custom Airtable Extension, the process is to select edit on the block, grab the URL/port from AT,  run the block locally with block --run, and select "Start Editing Extension." However, the Chrome setting (flag) that used to allow developers to host the app code locally and run it in AT has been removed. (The flag was #allow-insecure-localhost.) This leaves us unable to edit the extension. 

Any suggestions for how to get development working again for extensions/blocks? 

2 replies

Alexey_Gusev
Forum|alt.badge.img+12
  • Brainy
  • 1119 replies
  • December 15, 2024

Hi,

In flags, set "Temporarily unexpire M130 flags." to Enabled. Then chrome asks to relaunch, after that localhost flag setting will be visible. 


dilipborad
Forum|alt.badge.img+10
  • Brainy
  • 215 replies
  • December 16, 2024
Alexey_Gusev wrote:

Hi,

In flags, set "Temporarily unexpire M130 flags." to Enabled. Then chrome asks to relaunch, after that localhost flag setting will be visible. 


Hello @this-sam,
Try Firefox and search for how to set up the same settings(allow-insecure-localhost) on Google.
I think it's working on Firefox. 👍


Reply