react-native-template | Echobind 's template for React Native projects | Frontend Framework library

Resolved: i had to remove react native cli using yarn too

yarn remove global react-native-cli

You can use --strict in your compiler options.

This will:

Enable all strict type checking options. Enabling --strict enables --noImplicitAny, --noImplicitThis, --alwaysStrict, --strictBindCallApply, --strictNullChecks, --strictFunctionTypes and --strictPropertyInitialization.

Source: https://www.typescriptlang.org/docs/handbook/compiler-options.html

I'm not sure why this is happening but you can also use vscode terminal to build your apk:

You can generate a private signing key using keytool. On Windows keytool must be run from C:\Program Files\Java\jdk1.8.0_231\bin(or anywhere your jdk is):

Ok. There are multiple things that I am doing wrong in the above question.

1. Use type = 'table' instead of type = 'TABLE' in the select query to check the database. I was going through some online search results and observed this.

2. Rewrite componentDidMount and checkFirstTimeUsage methods as below

componentDidMount

In a word, no. You'll have to do it manually.

The templating system is quite dumb it basically creates a new react-native project and then copies the files that are included in the template and then installs the dependencies that have been listed.

As you will undoubtably updated files that were included in the original template, you wouldn't want to just install it over your existing project and hope for the best. That would cause you lots of problems. You may also have installed dependencies that require linking with native code, the template wouldn't specifically know about these changes.

So how can you update to the new template? Well it really depends on what you have done to the project. Unfortunately there is not going to be an easy way to do it.

To see what the major changes are between the templates I would look at the files included in the release that you are currently using, and the release that you plan to use and create a diff this can be done using the following command

diff -ur b a > ba.diff

where a and b are the directories that you are comparing.

Unfortunately the template that you are using doesn't create releases on their github https://github.com/maykonmichel/react-native-template-ez-devs/releases

You could attempt to download them off of their npm page https://www.npmjs.com/package/react-native-template-ez-devs .

Ultimately you can compare the changes on their github by looking at the commit history, you could look at the changelog if it existed, you can also look at the dependency versions that they are using and see if they have differed from the ones that you have used.

You can use github to do your compare Here is an example of the comparison between the most recent commit and one from a few days before. https://github.com/maykonmichel/react-native-template-ez-devs/compare/f4ffa06..04a1b8c

--== UPDATE ==--

I wrote a blog post that pretty much reiterates what I've written below, but I think it's a bit more clear and comprehensive.

https://medium.com/@chris.geirman/the-1-2-3s-of-react-native-templates-1f5dda037e11

I've seen that article and have been meaning to give it a try for some time, so I thought I'd take this opportunity to do that and also help you out at the same time

You left out many details in your description, and because I cannot confirm whether you did them in the same way as the article or not, I thought they'd be worth reiterating the key points. Plus, I thought the article might be a bit vague. So here's what worked for me.

Note: If you're sure you've done everything correct, then you may be able to skip to section 4 - publish. Your main problem might just be how you've run your cli command.

You mentioned a tiny part of what your package.json looks like, but the article specifies that your dependencies should go into a new file named dependencies.json. If your dependencies were these, then that file would look like this (note: my template is only dependent on react-navigation)...