Resolve Android App Google Play Rejection -- 2

@extreamcode

Hi, With over 15 years of experience as a Full-Stack, AI, Network, and Systems Engineer, I am well-equipped to handle the complexities of resolving your Google Play Console rejections. I have extensive knowledge in Android app development using Java and have always prioritized compliance with Google Play Policies when building apps. My abilities extend beyond just coding - I am adept at navigating complex manifest conflicts and ensuring strict compliance with privacy policies. Throughout my career, I have consistently demonstrated my capacity to turn complicated requirements into functional software. In relation to your project, this entails performing a thorough examination of your Merged Manifest for hidden permission injections, removing them using tools:node="remove", as well as investigating your Google Play Console testing tracks to ensure clean builds override any past permissions. As an added value to my services, I offer a 30-Day Guarantee with Full Support Coverage After Project Completion which guarantees that I will provide post-launch support for any issues you may encounter. In addition to my technical proficiency, one of my key strengths is my ability to effectively communicate with clients. This will be paramount in guiding you through the process of filling out the remaining "App Content" declarations/questionnaires using the appropriate compliance terminology. My primary goal is to help you release your amazing Thanks!

@rashidamjad

Hello Circles Co., I understand the pressure of resolving the Google Play rejection loop for Memora Kids. I will perform a thorough merge-and- removal pass on the Android manifest to guarantee hard removal of deprecated permissions (including QUERY_ALL_PACKAGES, BIND_ACCESSIBILITY_SERVICE, and ACTIVITY_RECOGNITION) using a robust toolchain approach. I will: (1) audit the merged manifest and all relevant build variants for hidden artifacts; (2) validate and enforce removal via explicit manifest-scan rules and a no-remnant policy across all flavors/tracks; (3) inspect internal/closed testing tracks and any artifact bundles to identify legacy declarations and ensure override/dep recs; (4) align App Content questionnaire language with compliant, auditable terminology that accurately reflects current permission usage; (5) provide a repeatable CI hook to prevent regressions and document steps for future audits. The deliverable will be a clean, compliant AAB ready for review, with a detailed audit report and a step-by-step remediation plan. What specific regulatory or internal policy goals should we emphasize in the App Content declarations to ensure a fast, compliant review and prevent future rejections?

@Herculesz

Hi, this looks less like a coding task and more like a release-compliance diagnosis inside an existing Android delivery pipeline, which is usually where these rejections get stuck. The real engineering risk is misidentifying the rejection source and patching the wrong layer, whether that is manifest/config, policy declarations, permission usage, SDK compliance, or reviewer-visible behavior. I usually structure this kind of work as a short forensic pass first: review the Play Console notice, compare it against the submitted artifact, trace any recent changes, and isolate whether the failure is technical, policy, or documentation-driven. I have built and repaired live systems where the main job was entering an existing codebase, finding the actual fault line, and documenting the fix clearly. The closest examples are Custom Feature Development & Integration for codebase review and targeted remediation, and TikTok AI Livestream Setup for end-to-end troubleshooting under production constraints. Given the JD mentions Java and PHP, I would focus on the Android release surface first, then verify any backend-linked behavior that could affect reviewer flows or declarations. If useful, I can start by reviewing the rejection notice and mapping the likely remediation path before any code changes. Thanks, Hercules

@mrresearcher99

Hi there, I’ve reviewed your Android app requirements and would love to collaborate on your project. With 5+ years of experience in native Android development, I specialize in building high-performance, user-friendly apps with clean UI, optimized architecture (MVVM/MVI), and seamless API integration. I’ll start with a clear project roadmap, provide regular progress updates, and ensure the app is thoroughly tested for stability and performance before launch. Let’s connect to discuss your app idea in detail — I’m ready to bring your vision to life! Best, Bhargav Android Developer | Kotlin & Java Expert

@ahmedaaalnaasan

مرحباً، نحن فريق عمل متكامل نمتلك خبرة تتجاوز 10 سنوات في تطوير تطبيقات Android، البرمجة، الأمن التقني، التسويق الرقمي، وإدارة أنظمة Google Play Console. لدينا خبرة قوية في معالجة مشاكل رفض التطبيقات وسياسات Google Play، خصوصاً المتعلقة بـ QUERY_ALL_PACKAGES وAccessibility Services وPermissions Conflicts داخل ملفات الـ Manifest وعمليات الـ Build وAAB. نستطيع تحليل المشروع بالكامل، مراجعة الـ SDKs والـ Dependencies، فحص Manifest Merge، وتنظيف جميع الـ Legacy Builds أو Testing Tracks التي قد تسبب تعارضات مع أنظمة Google Play، بالإضافة إلى إعداد نسخة متوافقة بالكامل مع سياسات المتجر لتجاوز حلقة الرفض الحالية. نتحدث العربية والإنجليزية بطلاقة، ونلتزم بالتحليل الدقيق، التواصل المستمر، وتسليم حل احترافي ومستقر جاهز للنشر.

@codefusion53

Hi, I reviewed the issue carefully, and this looks like a Google Play policy and build artifact conflict rather than a normal Android bug. I can help inspect the final merged manifest, identify whether QUERY_ALL_PACKAGES, BIND_ACCESSIBILITY_SERVICE, or ACTIVITY_RECOGNITION are still being injected by dependencies, and enforce removal with proper manifest rules where appropriate. I have experience with Android app releases, Google Play Console review issues, sensitive permission declarations, SDK audits, foreground service compliance, testing track cleanup, and rejection troubleshooting. For this case, I would check the clean AAB, dependency tree, merged manifest, Gradle outputs, and every active Play track to confirm whether old bundles are still influencing policy forms. I can also help prepare clear App Content declaration wording and compliance notes so Google understands the deprecated features were fully removed and the current app flow no longer uses those sensitive permissions. Best, Justin

@topcreator100

Hi there Circles Co team, I’ve read your memo about Memora Kids and the stubborn Play Console rejections tied to QUERY_ALL_PACKAGES and BIND_ACCESSIBILITY_SERVICE even after a clean AAB. I’m confident I can trace hidden manifest injections and remove them for good, then clean up the testing tracks so you’re not flagged by old bundles. I’ll audit the merged manifest with node="remove" rules to forcefully strip any legacy artifacts, and I’ll map out a clear remediation path for the App Content declarations to align with Google policy. Best regards,

@toriquldev123

Hello dear, Greetings from MD. Toriqul Islam! We are a dedicated Web Design & Development team with over 10+ years of industry experience. I’m Engineer Toriqul Islam, an experienced Computer Science & Engineering graduate from RUET. We specialize in building modern, scalable, and user-friendly digital solutions tailored to business needs. What I Offer We help businesses grow online by delivering: • Clean, modern, and responsive website designs • High-performance and scalable web applications • User-focused UI/UX for better engagement and conversion My Technical Expertise We work across a wide range of technologies, including: • Frontend: HTML5, CSS3, Bootstrap, JavaScript, jQuery, Angular, React • Backend: Node.js, PHP, Laravel, .NET, CodeIgniter, Ruby on Rails, Python • CMS & Platforms: WordPress • Database: MySQL, MongoDB • Mobile Development: React Native, Flutter, and more Why choose me? ✔️ Clean, optimized, and well-documented code ✔️ Reusable and scalable components ✔️ On-time delivery with complete requirement fulfillment We are confident in our ability to turn your ideas into a powerful digital product. Let’s discuss your project and make it a success. Looking forward to working with you! Best Regards, Md. Toriqul Islam

@mayankinnovative

Hi, As per my understanding: You’re facing a Google Play rejection loop where deprecated sensitive permissions like QUERY_ALL_PACKAGES, BIND_ACCESSIBILITY_SERVICE, and ACTIVITY_RECOGNITION are still being detected despite removing related functionality from the current codebase. The likely causes are merged manifest injections from SDKs or legacy AABs remaining active in older Play Console tracks. Implementation approach: I will begin with a complete audit of the merged manifest, Gradle dependencies, and generated APK/AAB outputs using Android Studio APK Analyzer and manifest inspection tools to identify hidden permission injections. Any unwanted permissions will be forcefully removed using manifest overrides and tools:node="remove" strategies where applicable. Next, I’ll review all Play Console tracks (internal, closed, production) to identify legacy artifacts still triggering automated scans and help retire or supersede them properly. I’ll also assist with Play Console App Content declarations using policy-compliant wording aligned with Google’s latest sensitive permission requirements to minimize further automated rejections. A few quick questions: 1. Which SDKs/services are currently integrated in the app? 2. Do you still use any AccessibilityService or UsageStats-related modules internally? 3. Can you share the latest merged manifest and rejected AAB version details? 4. Have all old testing-track releases been fully deactivated or only unpublished?

@markupdudes

Hi Circles Co. Team, I understand the urgency and complexity of the rejection loop you're experiencing with "Memora Kids" due to sensitive permissions issues on Google Play. With my extensive experience in Android development and deep expertise in Google Play Policy compliance, I can thoroughly audit your merged manifest to identify any hidden permission injections. I'll also analyze your testing tracks to root out legacy builds causing conflicts, ensuring all problematic permissions are fully disabled or removed. Furthermore, I will assist you in accurately completing the "App Content" declarations with precise compliance language to satisfy Google's automated checks. I propose to start with a deep manifest inspection and track audit immediately, aiming to resolve the issue within 5 days. Together, we can get your app compliant and back on the Play Store swiftly. Could you please share access to your Google Play Console and the most recent app bundle to start the audit? Best regards,

@rishidarkunde

As an experienced full-stack developer with over 9 years in the industry, I understand the criticality of delivering quality work without delays or excuses. I have a proven track record of untangling complex issues and guiding apps to Google Play Store compliance. My expertise extends not only to Android App Development but also to Website Performance Optimization, and Security & Malware Cleanup - skills that can come in handy while handling your app's rejection loop and manifest conflicts. I am well-versed in handling high-level Google Play Policy compliance, a skill that is of utmost importance for your project. Navigating through the complexities of manifest injections and removing hidden permissions is something I have excelled at during my professional journey. Moreover, my technical knowledge of React Native, React.js, Node.js, Laravel, PHP matches well with your project requirements. I value clean code and client satisfaction above everything else. Hence, with me as your developer, you can expect the cleanest of codes, fast delivery, and zero drama. Don't let the AI bots stand between you and the release of your essential parental control app. Let's get it done right away.

@devbaloni1983

Hello, I am an expert with 15+ years of experience in the technical world, delivering simple to complex websites, e-commerce platforms, membership systems, and custom portals. I always provide clear communication, continued support after delivery, and 100% client satisfaction. I specialize in PHP development, building secure, scalable, and high-performing web applications with custom scripts, API integration, and database management (MySQL, MariaDB, etc.). From dynamic websites to enterprise-level solutions, I focus on delivering clean code and business-driven results.

@Kaki08

Hi Have a Pleasant day ! I carefully had read your requirements in your job post on freelancer.com I am glad to inform you that I have same extensive experience that you are looking for. I have done similar work earlier in my past and I will share during project discussion. Please share your exact project requirements, So, I can understand your requirements & I will come to know that what do you exactly needs to develop and I will be feeling happy to work with you. Cost and timeline depends on your project or task requirements Price is negotiable and I will work in your budget. No upfront payment will be charged. Always work in milestones. Looking forward for your positive response. Kind Regards, Sneha Kanwar

@ivicab6

Hi, I've worked on integrating complex apps with Google Play policies, ensuring compliance and resolving permission conflicts. I can help you audit your testing tracks, inspect the merged manifest for hidden permissions, and guide you through the App Content declarations to ensure a smooth release. Let's start with a small audit to align before tackling the larger issue. Best Regards, Ivica

@nicolasalexandro

Hey — saw your post about fixing the Google Play rejection for sensitive permissions in your Android app. When Google flags an app for permissions, it’s usually a mix of manifest + Play Console settings + policy declaration being slightly out of sync. Quick question before I suggest an approach: Do you already have the exact rejection message from Google Play (with the policy name) and a recent Play Console screenshot? I’ve handled multiple Play Store rejections around sensitive permissions (location, phone, SMS, etc.) and got them approved by tightening the manifest, updating the permission flow, and aligning with Google’s policy wording. If you send the rejection email, your manifest, and the Play Console link or screenshots, I can review them and tell you the clearest path to get this approved.

@srdjan9494

Hello, For the QUERY_ALL_PACKAGES / BIND_ACCESSIBILITY_SERVICE rejection loop, I would not assume the source is only your current codebase. I’d audit 3 layers in parallel: merged manifest (./app/build/intermediates/merged_manifests), transitive SDK permission injection, and hidden Internal/Closed track AABs still being scanned by Google Play. Day 1 deliverable: permission trace report showing exactly which dependency/build introduces each sensitive permission, enforced removals via tools:node="remove" where needed, plus a Play Console cleanup checklist for tracks + App Content declarations. One important question — are you building with native Android Gradle only, or is Memora Kids using Flutter / React Native dependencies that could be contributing hidden manifest entries? Looking forward to working with you. Srdjan

@craigd43

Drawing on my experience as an Android and Java developer, I bring to the table a deep understanding of Google Play Policy compliance, which I see is a key requirement for your project. In addition to having experience handling Foreground Services and dealing with complex manifest conflicts, I have successfully managed high-stakes projects in the past - similar to what you are facing. My ability to not just identify hidden permission injections but also effectively enforce their removal by using tools like 'node="remove"' will go a long way in eliminating recurring rejections for your 'Memora Kids'app. Another reason why I am confident about solving your issue lies in my unique perspective drawn from extensive work with third-party SDKs. This has familiarized me with silent permissions injection challenges, enhancing my ability to navigate through them effectively and completely. I am also very comfortable working with any testing track related issues that might be adding to the rejections on Google Play. Lastly, I take immense pride in delivering tangible results that surpass client expectations and make a real difference. So, if given the opportunity, I will not only fix your current problem but also ensure that you are well-equipped to face similar issues in the future through providing detailed guidance on filling out future app content declarations. I look forward to getting started on solving this critical challenge for you!

@guptakishan805

With over a decade of experience in Android development, I'm no stranger to navigating the complicated terrain of Google Play policies and resolving App compatibility issues. My approach to your project will be thorough and systematic, covering the full scope of what you need: from identifying any hidden permission injections, ensuring hard removal using "tools:node="remove"", auditing testing tracks, to guiding you on how best to fill out the remaining "App Content" declarations/questionnaires. My track-record shows that I’m not only good at fixing technical issues, but also at building scalable platforms with clean architecture like your parental control app. This means I am going to use my skills not only for just debugging the problem but also looking for a long-lasting solution which serve as a basis for an improved architecture of features for your app. In addition to my strong technical aptitude, I offer clear communication, reliable execution and most importantly; a commitment to long-term collaboration. I understand the value of building strong partnerships with clients and am wholeheartedly invested in helping you overcome this hurdle so we can get your valuable app back on track. Let's work together to give your parental control app, "Memora Kids," the release it deserves!

@adisonw

Dear Sir, I am thrilled to bid your project. I can help audit and resolve the Google Play rejection loop for Memora Kids by checking the merged manifest, dependency permissions, legacy testing-track artifacts, and App Content declarations. I have experience with Android manifest merging, sensitive permission cleanup, Play Console review issues, foreground/service declarations, and policy-focused release troubleshooting. My approach would be to inspect the final merged AAB manifest, identify whether QUERY_ALL_PACKAGES, BIND_ACCESSIBILITY_SERVICE, ACTIVITY_RECOGNITION, or related permissions are still injected by dependencies, then apply proper tools:node="remove" rules and rebuild verification. I can also help review internal/closed/open testing tracks for old active bundles, guide replacement or deactivation steps, and prepare compliant wording for the Play Console declarations so the clean build is clearly represented. One important question: do you already have access to the generated merged manifest or APK/AAB analyzer output from the latest rejected build? Sincerely, Adison.