Android Manifest Map error in react native - reactjs

I get this error when click listing in android devices.. attach listing error and sentry report.
if need update AndroidManifest.xml .. i found so many AndroidManifest.xml in my source.
https://user-images.githubusercontent.com/25501496/62419485-dcb8a380-b6b3-11e9-99bb-a0780134638d.jpeg
https://user-images.githubusercontent.com/25501496/62432060-fdd6ce00-b75f-11e9-81de-11519a131125.jpeg
i tried add code in android manifest file..but i check got too many files
im using template from codecanyon " Listapp "

You need to add your API key in your AndroidManifest.xml file (which is usually located in app\src\main), within the <application> element, like the error message indicates.
<meta-data
android:name="com.google.android.geo.API_KEY"
android:value="YOUR_API_KEY"/>
Hope this helps.

in the meta-data tag, it must be:
<application>
<!-- You will only need to add this meta-data tag, but make sure it's a child of application -->
<meta-data
android:name="com.google.android.geo.API_KEY"
android:value="Your Google maps API Key Here"/>
</application>

Related

Any idea how to add manifest.json to html head dynamiclly

I realized that, by default, the umi project does not have manifest.json. I added the file to the public folder manually. Then, after compiling the application through the umi build command, my custom file is merged with thedist folder.
But is there any way to add the meta header to the self-generated index.html file?
I have not been able to find anything in the UMI docs. My guess, I need to build a script to insert it into the file after it is fully compiled.
Anything would be helpfull.
If you are using the pro.ant.design, you can find the index.html in /src/pages/document.ejs. It is a templated version of the index page.

how do I configure a codenameone project to install on external storage in Android

I am trying to get my codenameone application to install to external storage, so I do not need root permissions to debug what is writes to storage, as it does not work on Android, even if it does in the simulator.
First I assumed just having codename1.arg.android.installLocation=preferExternal in codenameone_settings.properties would do just that, but the application still installs to internal storage even after changing that installLocation to preferExternal from auto.
So I thought perhaps it needs quotes for the preferExternal, and proceeded to give them (=\"preferExternal\") - this gives a manifest build error on the build server, which shows the manifest with double quotes, so the original was the correct form.
From the error report, I saw that
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:required="false" />
so I thought perhaps this needs to be required for the install to external storage to actually be possible. I tried adding codename1.arg.android.permission.WRITE_EXTERNAL_STORAGE=true to the properties file like the documentation would suggest, but that fails in manifest merge:
Merging result: ERROR
/tmp/build6786351350686020379xxx/happy2/src/main/AndroidManifest.xml:48:7-69 Error:
Element uses-permission#android.permission.WRITE_EXTERNAL_STORAGE at AndroidManifest.xml:49:5-81 duplicated with element declared at AndroidManifest.xml:45:5-106
/tmp/build6786351350686020379xxx/happy2/src/main/AndroidManifest.xml Error:
Validation failed, exiting
Ok, so I thought that is always included, and thus I just need to change the required setting to true, and followed what the documentation says by adding codename1.arg.android.permission.WRITE_EXTERNAL_STORAGE.required=true to the properties. This builds, but the actual permission is not set to android:required="true", but remains false.
Using android.xpermissions tag to insert the wanted line <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:required="true" /> does insert it to the manifest, but manifest builder gives and error since the default false line will still be there too:
Merging result: ERROR
/tmp/build5902390972256151175xxx/happy2/src/main/AndroidManifest.xml:48:3-103 Error:
Element uses-permission#android.permission.WRITE_EXTERNAL_STORAGE at AndroidManifest.xml:48:3-103 duplicated with element declared at AndroidManifest.xml:45:5-106
/tmp/build5902390972256151175xxx/happy2/src/main/AndroidManifest.xml Error:
Validation failed, exiting
So the question remains, how do I configure a codenameone project to install on external storage in Android?
See this android:installLocation="preferExternal" not working
The gist is that parts of your app will always install in the hidden area and storage will probably go there.
If you want to write stuff to the SD card you can do that with the FileSystemStorage API which allows you to write to arbitrary roots. You can detect the SDCard root and just write there. I would suggest debugging in the simulator though where you can see the content of storage easily in the .cn1 directory.

DNN custom skin and css deployment

I am new to this and trying to figure this out. I have created a internal.ascx page and a Internal.css file for my internal page for a website. If I create a new page in DNN and apply this new skin it doesnt seem to apply the CSS. I copied the both ascx and css file to the _default/Skins/ folder.
Have also tried adding in the css via the following code
<dnn:DnnCssInclude runat="server" FilePath="/Internal.css" PathNameAlias="SkinPath" />
Nothing seems to be working. Have cleared my cache and tried different machine to view the page. But the style is still not coming through.
Thanks in advance
Create a new folder in the _default/Skins/. For example, call the folder "Internal" (/Portals/_default/Skins/Internal). Copy your ascx and css skin files into there. Rename the css to "skin.css". You shouldn't need to reference it in the ascx since DNN will pick it up based on the name.
Also, the reason your CSS include statement may not have worked was because filepath "/Internal.css" was probably trying to look for it in the root of the website. I would think it would simply be "Internal.css". But you could verify in Firebug what path it generated.

How to Programatically Create Page on Module Installation?

I have a custom DNN module that I'm working on that I need to create an Admin Page when the module is installed within a DNN instance. I have creating the page handled, but getting code to run when the module is installed/upgraded is something I haven't figured out.
How do you wire up code to be executed as part of the installation/upgrade of a DNN module?
I've been successful with using IUpgradeable as part of the install. You specify a method in a core module class (FeatureController.cs if using the Christoc.com template) in the dnn install manifest file.
This [class].UpgradModule is executed after the app restart (happens after a module install/config change for the module version(s) specified).
It's quite "elegant"...the DNN install schedules an "eventexecution" as specified in the manifest and you can run whatever code you desire.
My manifest (modulename.dnn) had an eventMessage attribute (placed after the desktopModule element). Ex:
<eventMessage>
<processorType>DotNetNuke.Entities.Modules.EventMessageProcessor,DotNetNuke</processorType>
<processorCommand>UpgradeModule</processorCommand>
<attributes>
<businessControllerClass>SSI.DNN.SSIReplicationModule.Controllers.FeatureController, SSIReplicationModule</businessControllerClass>
<desktopModuleID>[DESKTOPMODULEID]</desktopModuleID>
<upgradeVersionsList>00.00.01</upgradeVersionsList>
</attributes>
</eventMessage>
Whatever is in:
<businessControllerClass>SSI.DNN.SSIReplicationModule.Controllers.FeatureController, SSIReplicationModule</businessControllerClass>
With the method name:
<processorCommand>UpgradeModule</processorCommand>
will get executed at install.
Hope that helps...if you need code for the page creation and module add let me know.
My first SO post ever!!
Apparently, there's a new way to do it, but so far I haven't found documentation. It looks like this:
<desktopModule>
...
<page type="Admin" common="true">
<name>Configuration Manager</name>
<icon>~/Icons/Sigma/Configuration_16X16_Standard.png</icon>
<largeIcon>~/Icons/Sigma/Configuration_32X32_Standard.png</largeIcon>
<description>Modify configuration settings for your site</description>
</page>
....
</desktopModule>
Not sure when this was added, but I found it in source code of DNN 8.0.3.

How to include ext-js calendar in jsp?

I am new to EXT JS environment. I am working on a dynamic java project in eclipse indigo where i want to use ext-js calendar in one of my jsp.I saw the EXT_JS calendar demo from downloaded 'ext-4.1.1' sdk(index.html file in ext-4.1.1a\examples\calendar).
I want to create a .js file as like ext-js calendar page. So for that i followed the path given in
http://loianegroner.com/2010/11/spket-setting-up-eclipse-ide-for-ext-js-and-jquery-development/ to integrate ext-js in eclipse.
But now when i copy index.html to my webcontent folder then it is not working(Originally it is showing nothing). But when i copy the entire ext-js source code to my workspace web content then running the index.html file in example/calendar folder of ext-4.1.1a giving me required result.But I don't think this as a solution.
I could not find any way also how to start to do my task.
So Pls anybody help me here...
Regards :
Dev
When nothing shows up on the screen, it is commonly a case where the ExtJS library isn't loaded. Without seeing the code, it's hard to pinpoint the issue.
Using Chrome Dev tools or Firebug for Firefox, take a look at the console and/or network output.
The files you're looking for will be included in the <head> section of your index.html. There should be ext-all.js or possibly ext-all-debug.js at a minimum, plus the style sheets.
If this is your issue, then you need to include the proper paths to the ExtJS library. This can be the local installation, or you can use a CDN. For example:
<script src="http://cdn.sencha.com/ext-4.1.1-gpl/ext-all.js"></script>

Resources