Park App is a new mobile app which is capable of spotting animals in Sri Lankan national parks and uploading them. Since the targeted group of this app is normal users app need to have good logo. And the solution is to design a user attractive logo for the app.

Existing logo:

Logo requirements

Logo should be simple and effective.
Required outputs should includes .PNG and .SVG and any other

In pixels, the sizes are:

48 × 48,
72 × 72,
96 × 96,
144 × 144,
192 × 192

Describe the bug
Some cards do not expand to cover the entire width of the viewport. With this, every so often, there will be cards that take up half of their available space.

This poses both an aesthetic issue and a usability issue where this issue may be more apparent on smaller screen sizes.

To Reproduce
Steps to reproduce the behavior:

1. Build development version of the app
2. Launch development server
3. Open Elly app in an Android 10.0 virtual device
4. View parks screen
5. Scroll until you see the affected cards

Expected behavior
Cards take up the full viewport width.

Smartphone (please complete the following information):

• Device: Virtual Nexus 5X (running API 29 x86)
• OS: Tested on Android 10.0 and 9.0
• Browser: Not Relevant
• Version: Google APIs 29

Describe the bug
Upon trying to load the LandingScreen component, the app throws an error due to not having a call to firebase.initializeApp(). This is after configuring the config file in the React Native build, as well as adding the Google services plist.

To Reproduce
Steps to reproduce the behavior:

1. Follow developer instructions
2. Create iOS client and move the Google services plist to the root of the iOS build directory
3. Build application using xCode 11 with a target of 13.1
4. See error upon opening app

Expected behavior
Login screen to be displayed

Screenshots
If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

• Device: Virtual iPhone 11 Pro Max
• OS: iOS 13.1
• Browser: Not relevant
• Version: xCode 11

Additional context
Add any other context about the problem here.

Is your feature request related to a problem? Please describe.
The user is not given clear input as to what issue has arisen with their password.

The requirements are not listed, and it appears that a special character is required. With this, I believe that users may become confused at this login flow, not recognizing what the password constraints are.

Describe the solution you'd like
Rather than just displaying a blanket solution, the user should be presented with the validation rule that their password has failed.

Describe alternatives you've considered
An alternative to the above would just be to list the requirements, although this is not as interactive.

Is your feature request related to a problem? Please describe.
Related to starting the project as a contributor. There are a few errors that contributors may encounter that could be solved with a piece in the contributor documentation.

Describe the solution you'd like
Contributors may encounter issues with oAuth as they first have to enable the respective authentication methods within Firebase. Instructions on this would be appreciated in the contributor guide.

Additionally, there are custom rules (or a default template) that have to be applied to the Firebase database, or else the user encounters this error:

and the app gets stuck on a task

With this, mentioning the process in the documentation for setting up the database and providing the following rules:

{
    "rules": {    
        ".read": true,
        ".write": true
    }
}

may prove to be helpful for new contributors.

This error cannot be fixed even tried several times.

Describe the bug
The application, created by following the developer guide on Elly, throws an error upon trying to load the login/initial screen as a result of loading FormScreen. This component tries to load a config file two directories up that does not resolve correctly (doesn't exist in some configurations). With this, Elly had a similar issue, leading me to believe that there may be a missing step in the developer guide or an issue with using the Android 10.0 API (v29).

To Reproduce
Steps to reproduce the behavior:

1. Build development version of the app
2. Launch development server
3. Open Parks app in an Android 9.0 or 10.0 virtual device (Android 9.0 using Intel API)
4. See error

Expected behavior
Login form to be displayed

Screenshots
Error Logs:

Smartphone (please complete the following information):

• Device: Virtual Nexus 5X (running API 29 x86)
• OS: Tested on Android 10.0 and 9.0
• Browser: Not Relevant
• Version: Google APIs 29

Additional context
Google Services: com.dwc