A scan (see here for details and background) just revealed the APKs at your releases are signed using an expired debug key ("denyAfter 2019-01-01"). As that has security implications, may I ask you to please switch to a proper release key, and provide the corresponding APK signed with it? Thanks in advance!

Mochi. When I think of flutter (the word specifically), I think of sonething light and airy, but also dense at the same time. Mochi is thin and light on the outside, and has thick, decadent ice cream filling. It also kinda sounds like movie.

Hey, I am Pravin Nichal. I would like to contribute in this app can you please assign me task.
This is for my open source contribution class
please contact me at [email protected]

While your latest tag suggests a version of 0.0.2, the APK identifies the app as

package: name='com.example.movies_app_flutter' versionCode='1' versionName='1.0.0' compileSdkVersion='31' compileSdkVersionCodename='12'

According to your release history, it should read versionCode='2' versionName='0.0.2' instead. The problem originates here – this line in your pubspec.yaml should, for the current release, be

version: 0.0.2+2

and be adjusted with every release (right before tagging and building the APK). Could you please fix that? For some background:

• as the app would always show up as 1.0.0 regardless of the version installed, users would never know if they have the most recent release installed
• as versionCode is never changed, Android would consider them all the same version (it requires this to be increased with each release)

Thanks in advance!