Only unpacked extensions and apps installed from the Chrome Web Store can load NaCl modules without enabling Native Client in about:flags.

[DevelopDaily]

My app has already been published to the Web Store. After that, I am able to install it to my Chrome, but I still get the above message.

Meanwhile, I am able to access other NaCl apps in the web store such as the Native Client Examples without any problems.

Could you please advise me of what I have missed? I suspect my web store manifest.json has missed something. Could you share the manifest.json that is used to publish the Native Client Examples?

Thanks.

[Bill Budge]

First, make sure the URL for the .nmf file (NaCl manifest) is from an origin declared in your extension manifest. Before the NaCl plugin is started, Chrome searches for an extension using this origin. If no extension is found, it is considered a non-webstore app. The origin is usually the host and port, but extension manifests allow wildcards.

Second, make sure the app's installation is not corrupted by removing it and reinstalling.

[Colt McAnlis]

Hi, to supplement Bill's excellent response, these resources may shed some light on things:

http://developer.chrome.com/extensions/manifest.html

https://developers.google.com/native-client/dev/devguide/distributing

~Main