Issues Publishing Edge Extension

%3CLINGO-SUB%20id%3D%22lingo-sub-1203880%22%20slang%3D%22en-US%22%3EIssues%20Publishing%20Edge%20Extension%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1203880%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20posted%20about%20this%20on%20StackOverflow%20(%3CA%20href%3D%22https%3A%2F%2Fstackoverflow.com%2Fquestions%2F60478421%2Funable-to-publish-edge-browser-extension-package-acceptance-validation-error%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Elink%3C%2FA%3E)%20and%20I've%20created%20at%20least%20two%20tickets%2C%20still%20no%20luck%3A%20I%20believe%20there's%20a%20bug%20with%20package%20validation%20of%20Edge%20Extensions.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20now%20I%20created%20a%20bare%20minimum%20extension%20with%20an%20empty%20content%20script%20and%20no%20functionality%20and%20I'm%20still%20getting%20the%20error%3A%26nbsp%3BPackage%20acceptance%20validation%20error%3A%20Localization%20directory%20for%20default_locale%20en%20not%20found%20under%20_locales%20directory.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAttached%20is%20the%20archive%20that%20I've%20submitted%20that%20returned%20this%20error.%20As%20you%20can%20see%2C%20it%20has%20that%20directory.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1205016%22%20slang%3D%22en-US%22%3ERe%3A%20Issues%20Publishing%20Edge%20Extension%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1205016%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F571970%22%20target%3D%22_blank%22%3E%40msdevgeorgemike%3C%2FA%3E%2C%20I%20am%20sorry%20that%20you%20are%20experiencing%20this%20issue.%26nbsp%3B%20I%20have%20escalated%20this%20to%20see%20if%20there%20is%20an%20error%20in%20our%20ingestion%20process.%26nbsp%3B%20I%20hope%20that%20we%20can%20figure%20out%20what%20is%20going%20on%20here.%26nbsp%3B%20Thanks%20-%20Elliot%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1205075%22%20slang%3D%22en-US%22%3ERe%3A%20Issues%20Publishing%20Edge%20Extension%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1205075%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F239638%22%20target%3D%22_blank%22%3E%40Elliot%20Kirk%3C%2FA%3E%26nbsp%3B-%20Thanks.%20Appreciate%20it!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1206971%22%20slang%3D%22en-US%22%3ERe%3A%20Issues%20Publishing%20Edge%20Extension%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1206971%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F571970%22%20target%3D%22_blank%22%3E%40msdevgeorgemike%3C%2FA%3E%2C%20you%20were%20right%2C%20we%20did%20have%20a%20bug%20in%20our%20validation%20step.%26nbsp%3B%20We%20think%20that%20we%20have%20fixed%20the%20issue%2C%20and%20have%20also%20deployed%20the%20fix.%26nbsp%3B%20Please%20give%20it%20another%20try%20and%20see%20if%20it%20works%20for%20you%20now.%26nbsp%3B%20Thanks%20-%20Elliot%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1207045%22%20slang%3D%22en-US%22%3ERe%3A%20Issues%20Publishing%20Edge%20Extension%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1207045%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F239638%22%20target%3D%22_blank%22%3E%40Elliot%20Kirk%3C%2FA%3E%26nbsp%3B-%20It%20works!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1209562%22%20slang%3D%22en-US%22%3ERe%3A%20Issues%20Publishing%20Edge%20Extension%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1209562%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20glad%20that%20you%20are%20fully%20unblocked%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F571970%22%20target%3D%22_blank%22%3E%40msdevgeorgemike%3C%2FA%3E!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

I've posted about this on StackOverflow (link) and I've created at least two tickets, still no luck: I believe there's a bug with package validation of Edge Extensions. 

 

Just now I created a bare minimum extension with an empty content script and no functionality and I'm still getting the error: Package acceptance validation error: Localization directory for default_locale en not found under _locales directory.

 

Attached is the archive that I've submitted that returned this error. As you can see, it has that directory.

5 Replies
Highlighted

Hi @msdevgeorgemike, I am sorry that you are experiencing this issue.  I have escalated this to see if there is an error in our ingestion process.  I hope that we can figure out what is going on here.  Thanks - Elliot

Highlighted

@Elliot Kirk - Thanks. Appreciate it! 

Highlighted

Hi @msdevgeorgemike, you were right, we did have a bug in our validation step.  We think that we have fixed the issue, and have also deployed the fix.  Please give it another try and see if it works for you now.  Thanks - Elliot

Highlighted

@Elliot Kirk - It works!

Highlighted

I am glad that you are fully unblocked, @msdevgeorgemike!