How to fix App Service builds behind TLS proxies with a public certificate

August was a busy month for the Firebase team! 🐝 Catch the updates in the latest Firebase Release Notes. Chapters: 0:12 - Firestore updates 1:29 - App Hosting route-based monitoring 1:55 - Crashlytics updates 2:44 - Data Connect initialization from the CLI 3:00 - firebase init aitools 3:20 - ActionCodeSettings.link_domain in Admin SDKs 3:45 - Firebase App Distribution tester restrictions

The Playwright MCP server is a huge productivity boost to agents like #ClaudeCode and #GeminiCLI because it allows them to visit your app, interact with it live, take screenshots, and more. With your agent, you can specify which app state/page/config you’d like to screenshot, and repeat this with several different combinations/conditions. "hey Claude, take screenshots of my login form flow: one series with regular sign in, then with GitHub, and another with Google OAuth" Here's how: https://lnkd.in/g7W3qkpP #agents #codingagents #mcp

lets code the server file ............... const express = require(express) const app = express() app.listen(4000)

🚪 What is an API Gateway? Think of an API Gateway as the front door to your system. Instead of letting everyone knock on many doors (different backend services), you give them one entrance. The gateway takes the request, checks it, routes it to the right service, and returns the answer safely. 🔹 A short story In a conference app, the Attendee service was hidden deep inside the system. When the mobile team needed it, we didn’t want them calling the backend directly. So we put an API Gateway in front. Now, all the mobile app knows is → “call the gateway.” The gateway takes care of routing, security, and even collecting logs. For the app team, it feels simple. For the system, it’s safe and organized. ✅ Conclusion: An API Gateway keeps things simple for users and safe for systems — a win for both sides. 🚀 #APIGateway #APIArchitecture #Microservices #Backend #SoftwareEngineering #APIs #Proxy

Dear App Developers-- You may be tempted to disable the highly optimized and familiar device keyboard and substitute your own custom "keyboard"--really just a collection of buttons--in order to add a few shortcut buttons you think will be helpful. You are wrong. Whatever advantage your custom keys might offer are FAR outweighed by the irritation of forcing users to use an unfamiliar, crippled "keyboard". Just don't do it.

Firebase Auth loses authentication state on Android app restart - user gets logged out when app is killed and reopened I'm developing a Flutter app using Firebase Auth, and I'm experiencing a persistent issue where users get logged out every time they close the app completely (kill from recent apps) and reopen it. The authentication should persist automatically on mobile platforms, but it's not working. Problem: User logs in successfully ✅ User closes app normally (minimize) - stays logged in ✅ User kills app completely and reopens - gets logged out and redirected to login❌ main.dart: void main() async { WidgetsFlutterBinding.ensureInitialized(); try { await Firebase.initializeApp( options: DefaultFirebaseOptions.currentPlatform, ); await SecurityService.initialize(); AntiDebugService.startMonitoring(); ObfuscationUtils.executeDummyOperations(); } catch (error) { debugPrint('Initialization error: $error'); } runApp(const KhedamApp()); _initializeBackgroundServices(); } void _initializeBackgroundServices() async { try { FlutterError.onError = (Flutter https://lnkd.in/gV4xPETj

Play Integrity API: Securing Beyond SafetyNet Google’s Play Integrity API is the modern way to ensure requests come from genuine and untampered app installs. I started using it after SafetyNet was deprecated. Why it’s important: ✅ Prevents modified or rooted devices from abusing APIs. ✅ Ensures the request originates from the Play Store-installed app. ✅ Adds a layer of trust between client and server. Basic flow: • App requests an integrity token. • Google Play validates app/device integrity. • Token is sent to your backend. • Backend verifies token with Google’s API. 💡 If your app handles financial or sensitive operations, Play Integrity is a must-have. #AppSecurity #PlayIntegrity #SecureAndroid

🚀 Day 17 of 30DaysBackend Challenge Today’s topic — Email Verification 📧 Imagine someone registers with a fake email like abc@random.com (which does not even exist 😅). If there is no verification system, the app will soon be full of fake and spam users ❌ Solution: 1. User registers and the backend creates a unique token 🔑 2. A verification link is sent to the user’s email 📩 3. Only the real email owner can verify ✅ 4. A fake email will never be verified 🚫 This way, only genuine and verified users become part of the app. It is a small step, but it adds trust and authenticity to any app 👌 #30DaysBackend #BackendDevelopment #NodeJS #EmailVerification #LearningJourney

Step 1: Smoke Testing What: Check if the app launches and main flows work at a basic level (open app, login, homepage load). Why: If app crashes or can’t login, all other testing is wasted time. Smoke tests act as a gatekeeper to ensure build stability. Proof: Industry practice: Most teams use smoke tests as first defense to avoid testing unstable builds. Example: If login is broken, you don’t want to spend hours on promo code tests.

Implementing OAuth, also known as social login, reduces the friction of account creation and authentication. On top of the reduced friction, if we plan to launch a mobile application in the Apple App Store, we're required to offer Sign in with Apple if we're also offering any other social authentication. In this article, we will learn how to add Sign in with Apple to a Rails app. We will learn everything from configuring our Apple Developer account to integrating the authentication code.