Exciting News: Major Update to Our English Vocabulary App!

I'm thrilled to announce that our English Vocabulary App has just received a significant update on Google Play! 📱✨ Download Now After a long hiatus due to my heavy daily workload, I finally dedicated time to reimplement the app from scratch. The source code from the last release was unfortunately lost, but this gave me the opportunity to rebuild the app with even better features and ensure full compliance with Google's latest policy requirements. What’s New: * Complete Reimplementation: T

Post, Code and Quiet Time. Exciting News: Major Update to Our English Vocabulary App! By Errong Leng – 25 May 2024 – View online → Photo by Natalie Kinnear / Unsplash I'm thrilled to announce that our English Vocabulary App has just received a significant update on Google Play! 📱✨ Download Now After a long hiatus due to my heavy daily workload, I finally dedicated time to reimplement the app from scratch. The source code from the last release was unfortunately lost, but this gave me the opportunity to rebuild the app with even better features and ensure full compliance with Google's latest policy requirements. What’s New: Complete Reimplementation: The app has been rewritten from the ground up, making it more robust and user-friendly. Privacy First: Rest assured, this app does not collect any user data. You can check out our privacy policy here. Enhanced Content: The app now includes 16,515 words from the Corpus of Contemporary American English, with detailed English and Chinese meanings for each word. Perfect for Test Preparation: This app is an excellent tool for anyone looking to expand their English vocabulary, particularly for IELTS and TOEFL tests. Check out the demo video on YouTube to see the app in action: Watch Now I created a simple HTML page for our privacy policy, which is now hosted on GitHub Pages. You can view it here. Thank you for your continued support. I'm confident that this updated version of our app will be a valuable resource for improving your English vocabulary and achieving your language learning goals. Download the latest version now and start learning! Best, QZL Corp. Post, Code and Quiet Time. © 2024 – Unsubscribe

Map-based Implementations Deprecated: Overriding getDataSource in Spring Boot's DefaultBatchConfiguration

With Spring Batch 5.0, significant changes have been made regarding job repository and explorer configurations. The Map-based job repository/explorer implementations were deprecated in version 4 and completely removed in version 5. This necessitates customizing the default batch configuration to use a Jdbc-based implementation. Additionally, Spring Batch 5.0 mandates using the Jdbc-based JobRepository, and customizing the data source configuration can help keep batch job-related data separate fr

Post, Code and Quiet Time. Map-based Implementations Deprecated: Overriding getDataSource in Spring Boot's DefaultBatchConfiguration By Errong Leng – 24 May 2024 – View online → Photo by nilufar nattaq / Unsplash With Spring Batch 5.0, significant changes have been made regarding job repository and explorer configurations. The Map-based job repository/explorer implementations were deprecated in version 4 and completely removed in version 5. This necessitates customizing the default batch configuration to use a Jdbc-based implementation. Additionally, Spring Batch 5.0 mandates using the Jdbc-based JobRepository, and customizing the data source configuration can help keep batch job-related data separate from your production database. Here’s how you can override the getDataSource method in DefaultBatchConfiguration to achieve this. Step-by-Step Guide Create a Custom Batch Configuration Class: Extend DefaultBatchConfiguration and override the getDataSource method in your custom configuration class. Define the DataSource Bean: Define a DataSource bean within your custom configuration class or another central configuration class. Here's an example: import org.springframework.batch.core.configuration.annotation.DefaultBatchConfiguration; import org.springframework.context.annotation.Configuration; import org.springframework.context.annotation.Primary; import org.springframework.beans.factory.annotation.Qualifier; import org.springframework.context.annotation.Bean; import javax.sql.DataSource; import org.springframework.boot.jdbc.DataSourceBuilder; import org.springframework.batch.core.initializer.BatchDataSourceScriptDatabaseInitializer; import org.springframework.batch.core.configuration.BatchProperties; import org.springframework.jdbc.datasource.init.DatabaseInitializationMode; @Configuration public class CustomBatchConfiguration extends DefaultBatchConfiguration { @Override public DataSource getDataSource() { return customBatchDataSource(); } private DataSource customBatchDataSource() { DataSource dataSource = DataSourceBuilder.create() .url("jdbc:h2:mem:batchdb;DB_CLOSE_DELAY=-1") .username("sa") .password("") .driverClassName("org.h2.Driver") .build(); // Initialize batch datasource script BatchProperties.Jdbc jdbc = new BatchProperties.Jdbc(); jdbc.setInitializeSchema(DatabaseInitializationMode.ALWAYS); new BatchDataSourceScriptDatabaseInitializer(dataSource, jdbc) .initializeDatabase(); return dataSource; } } In this example: CustomBatchConfiguration extends DefaultBatchConfiguration. The getDataSource method is overridden to return a custom DataSource for batch jobs. customBatchDataSource method configures the data source properties, using H2 in-memory database. The batch datasource script is initialized to ensure that the necessary batch job tables are created. Ensure Configuration is Picked Up by Spring Boot: Make sure your custom configuration class is in a package scanned by Spring Boot. If not, use @ComponentScan on your main application class or another configuration class. Job Repository/Explorer Configuration Updates Map-based Implementations Deprecated: The Map-based job repository/explorer implementations were deprecated in version 4 and completely removed in version 5. Jdbc-based Implementation: In Spring Batch 5.0, the Jdbc-based JobRepository is the only supported implementation. The @EnableBatchProcessing annotation will configure a Jdbc-based JobRepository, which requires a DataSource bean in the application context. Using In-Memory Database for Batch Jobs: If you do not want batch job-related tables created in your production database, you can configure the batch job repository to use an embedded database like H2. This way, batch job metadata is stored in the in-memory database while your production data remains in your primary database (e.g., Oracle, Microsoft SQL Server, MySQL). For more details, refer to the Spring Batch Migration Guide. By following these steps, you can effectively customize the data source configuration for your Spring Batch jobs in a Spring Boot application while adhering to the latest updates in Spring Batch 5.0 and maintaining separation between batch job metadata and production data. Post, Code and Quiet Time. © 2024 – Unsubscribe

How to Generate an .aab File in a React Native Project for Google Play Console

When developing a React Native app and preparing it for release on the Google Play Console, it's essential to generate the correct file format. While APK files are commonly used, Google Play Console imposes a 100MB size limit on APKs. If your app exceeds this limit, you'll need to generate an Android App Bundle (.aab) instead. Here's a comprehensive guide on how to generate an .aab file for your React Native project. Why Use .aab Instead of .apk? * Size Limitation: Google Play Console allows

Post, Code and Quiet Time. How to Generate an .aab File in a React Native Project for Google Play Console By Errong Leng – 22 May 2024 – View online → Photo by Emilio Garcia / Unsplash When developing a React Native app and preparing it for release on the Google Play Console, it's essential to generate the correct file format. While APK files are commonly used, Google Play Console imposes a 100MB size limit on APKs. If your app exceeds this limit, you'll need to generate an Android App Bundle (.aab) instead. Here's a comprehensive guide on how to generate an .aab file for your React Native project. Why Use .aab Instead of .apk? Size Limitation: Google Play Console allows APK files up to 100MB. If your app exceeds this size, you must use an .aab file, which supports larger apps. Optimized Delivery: .aab files enable Google Play's Dynamic Delivery, optimizing app delivery to users based on their device configuration. Steps to Generate an .aab File 1. Open Your Terminal First, open a terminal or command prompt. 2. Navigate to the Android Directory Change your directory to your project's Android folder: cd path/to/your/project/android 3. Run the Gradle Bundle Command Execute the Gradle command to build the app bundle in release mode: ./gradlew bundleRelease On Windows, use: gradlew.bat bundleRelease 4. Locate the .aab File After the build process completes, find the generated .aab file in the following directory: path/to/your/project/android/app/build/outputs/bundle/release/app-release.aab Updating Version Code and Version Name Before generating the bundle, update the version code and version name in your project to ensure the new release is accepted by the Google Play Console. 1. Open build.gradle (App Module) Navigate to android/app/build.gradle. 2. Update versionCode and versionName In the defaultConfig block, increment the versionCode and update the versionName as needed: android { ... defaultConfig { applicationId "com.example.myapp" minSdkVersion 16 targetSdkVersion 30 versionCode 2 versionName "1.1" ... } } Summary To generate an .aab file for your React Native project: Open terminal and navigate to the android directory. Run the Gradle command: On Unix-based systems: ./gradlew bundleRelease On Windows: gradlew.bat bundleRelease Update versionCode and versionName in android/app/build.gradle if necessary. Locate the .aab file in android/app/build/outputs/bundle/release/. Important Note Remember, if your APK file exceeds 100MB, Google Play Console will not accept it. Instead, you must generate and upload an .aab file for your release. This not only allows for larger app sizes but also enables optimized app delivery through Google Play's Dynamic Delivery. By following these steps, you can ensure your React Native app is correctly packaged and ready for distribution on the Google Play Console, regardless of its size. Publishing to Google Play Store · React Native Android requires that all apps be digitally signed with a certificate before they can be installed. In order to distribute your Android application via Google Play store it needs to be signed with a release key that then needs to be used for all future updates. Since 2017 it is possible for Google P… React Native Post, Code and Quiet Time. © 2024 – Unsubscribe

react native: fix error for android release: Version code has already been used. Try another version code

When you receive the error "Version code 1 has already been used. Try another version code." during the process of uploading an Android App Bundle (.aab) to the Google Play Console, it means that the version code you are trying to upload has already been used for a previous version of your app. The version code must be unique for each release. Here’s how you can update the version code and version name in your Android project: Step-by-Step Guide to Update Version Code Open your project in An

Post, Code and Quiet Time. react native: fix error for android release: Version code has already been used. Try another version code By Errong Leng – 22 May 2024 – View online → Photo by Victor Rosario / Unsplash When you receive the error "Version code 1 has already been used. Try another version code." during the process of uploading an Android App Bundle (.aab) to the Google Play Console, it means that the version code you are trying to upload has already been used for a previous version of your app. The version code must be unique for each release. Here’s how you can update the version code and version name in your Android project: Step-by-Step Guide to Update Version Code Open your project in Android Studio: Navigate to your project directory and open it in Android Studio. Locate the build.gradle file: Find the build.gradle file for your app module (usually located at app/build.gradle). Update the version code and version name: In the build.gradle file, look for the defaultConfig block. It should look something like this: android { ... defaultConfig { applicationId "com.example.myapp" minSdkVersion 16 targetSdkVersion 30 versionCode 1 # update version code versionName "1.0" # update version name ... } } Increment the versionCode to a new integer value. The versionCode must be a positive integer and greater than the previous version codes used. Optionally, you can also update the versionName to reflect the new version. This is typically a string like "1.0.1", "2.0", etc. Example: android { ... defaultConfig { applicationId "com.example.myapp" minSdkVersion 16 targetSdkVersion 30 versionCode 2 versionName "1.1" ... } } Sync the project: After updating the build.gradle file, sync your project with the Gradle files by clicking "Sync Now" in the yellow notification bar that appears at the top of the editor, or by selecting "File" > "Sync Project with Gradle Files". Rebuild your project: Rebuild your project to generate the new .aab file with the updated version code. You can do this by selecting "Build" > "Build Bundle(s) / APK(s)" > "Build Bundle(s)" from the menu. Upload the new .aab to Google Play Console: Once the build process is complete, locate the new .aab file in your project directory (usually in app/build/outputs/bundle/release/). Upload the new .aab file to the Google Play Console. Summary Open build.gradle (app module) in Android Studio. Increment versionCode and update versionName. Sync project with Gradle files. Rebuild your project to generate a new .aab file. Upload the new .aab to Google Play Console. By following these steps, you should be able to resolve the error and successfully upload your new version to the Google Play Console. Post, Code and Quiet Time. © 2024 – Unsubscribe