[Azure App Service] App Service builds behind proxies: fixing trust with a public certificate. TL;DR: If your organization uses a TLS-inspecting proxy (e.g., Zscaler), some of the traffic originating from App Service build infrastructure may be re-signed by the proxy. App Service doesn’t trust that proxy cert by default, so the build fails. Set the app setting WEBSITE_INSTALL_PUBLIC_CERTS_IN_KUDU=true and upload the proxy’s public certificate (.cer). App Service will install the certificate and your builds will succeed. https://lnkd.in/gRzpgV3k

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)

Yay! We have just released a new version of our Domino based push notifications system that powered by Twilio! ..and this time, it's Android 15+ ready! Prominic Verify is now v1.3.2. Latest release includes Google's API level 31+ and 16KB page sizes support. The app is now available at Google Play Store: https://lnkd.in/g-KaJNTs #domino #twilio #prominic #verify #prominicverify #push #notification

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

🚀 Notification is essential for every web app – from OTPs and reminders to real-time updates. I recently published @dhruvdobariya/notification-provider on npm 🎉 ! 🔹 Supports multiple providers: Firebase, OneSignal, Pusher 🔹 Provides automatic failover – if one provider (e.g., Firebase) goes down, it switches to the next one 🔹 Simple, unified API for sending SMS, push notifications, and real-time events. 👉 Install with: 🔹 npm install @dhruvdobariya/notification-provider ⚡ In just 2 days, almost 200 developers found it useful — super excited to see this adoption! 🙌 ✨ For more, explore here: https://lnkd.in/d7pKm4HM

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.

🚀 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

Debugging a Real Issue in App Soppose sales team reported: “Some users can’t see any data, it just keeps loading…” After digging in, you found: the JWT Token Expiration With JWTs, each token has a fixed expiry. Once expired, the server will reject requests — so the app just kept waiting without success. Lesson: Always handle expired tokens gracefully. For apps using only JWTs, that means prompting the user to log in again instead of leaving them hanging. Have you faced this challenge in your apps? How did you solve it? #JWT #Authentication #MobileAppDevelopment #UserExperience