Saturday, September 19, 2026

Mobile App without Device Testing using AWS Device farm


Part 1: Create the project

  1. Open AWS Device Farm.

  2. On the left menu, look for Mobile Device Testing.

  3. Select Projects.

  4. Click Create a new project.

  5. Enter:

Project_name Enterprise QA
  1. Click Create project.

If you cannot see Projects, click the ☰ menu in the upper-left corner.

Part 2: Start an Android remote session

Inside the newly created project:

  1. Open the Remote access tab.

  2. Click Start a new session.

  3. Enter a session name such as:

Project_name Android Smoke Test
  1. Under device selection, select Android.

  2. Initially choose one commonly used device, such as:

Samsung Galaxy S23/S24
Google Pixel 7/8
  1. Choose a stable Android version supported by the project app.

  2. Select an available device.

  3. Click Confirm and start session or Start session.

AWS may take several minutes to prepare the physical device.

Billing normally starts when the device session begins. Do not leave the session running unnecessarily.

Part 3: Upload and install the APK

When the remote Android device appears:

  1. Find Install application, Upload application, or the upload icon.

  2. Select:

project_name.apk
  1. Wait for AWS to upload and install it.

  2. Open Medicalin from the device.

  3. Perform this initial smoke test:

  • App installs successfully

  • App opens without crashing

  • Logo and first screen display correctly

  • Login page loads

  • Test account can log in

  • Dashboard loads

  • Basic navigation works

  • Logout works

  • No obvious layout problems

  • Backend connection succeeds

Take screenshots of any errors. AWS should also provide device logs and session information.

Part 4: End the Android session

When testing is complete:

  1. Click End session or Stop session.

  2. Confirm the session has ended.

  3. Record:

Device:
Android version:
APK version:
Installation: Pass/Fail
Launch: Pass/Fail
Login: Pass/Fail
Issues:
Session ID:

Ending it is important because Device Farm charges by device minute after the free allowance. AWS currently advertises a one-time 1,000-device-minute free trial, followed by $0.17 per device minute. AWS Device Farm pricing

Part 5: Test the iOS IPA

Return to your project:

  1. Open Remote access.

  2. Click Start a new session.

  3. Name it:

Project_name iOS Smoke Test
  1. Select iOS.

  2. Choose an available iPhone.

  3. Prefer an iOS version supported by the project.

  4. Start the session.

  5. When the iPhone is ready, choose Install application.

  6. Upload:

project_name.ipa
  1. Wait for installation and launch the app.

  2. Repeat the same login and navigation checks.

  3. End the session immediately after testing.

If AWS rejects the IPA, copy the exact error. Common causes include:

  • Invalid or incomplete code signing

  • Unsupported provisioning

  • Missing application entitlements

  • IPA built for the simulator instead of a physical iPhone

  • Corrupted IPA package

The development team may need to produce a new physical-device .ipa.

If you receive “Access denied”

Your AWS user may need Device Farm permissions. For initial testing, the administrator can attach:

AWSDeviceFarmFullAccess

A restricted custom policy is safer for long-term use, but the managed policy is simpler for the first controlled test.


Saturday, September 5, 2026

Integrate Sentry with AI Agents

 To get Sentry set up for production error tracking:

1. Create a Sentry project
- Sign up at [sentry.io](https://sentry.io) (free tier covers most apps)
- Create an organization and a React project
- Note these three values:
  - SENTRY_ORG — your org slug (from the URL: `https://<org>.sentry.io`)
  - SENTRY_PROJECT — the project slug
  - SENTRY_AUTH_TOKEN — Settings → Auth Tokens (Organization Tokens). Just click "Create New  (needs `project:releases` and `org:read` scopes)

2. Add them to your AI developer Agent
Add these as Build Secrets in your workspace:
- Go to Workspace Settings → Build Secrets
- Add `SENTRY_AUTH_TOKEN`, `SENTRY_ORG`, and `SENTRY_PROJECT`
- These are injected during `bun run build`, so the source-map upload plugin can authenticate

3. About “automatically fixing errors”
Sentry does not auto-fix code by itself. What it can do:
- Capture errors with stack traces, release version, and user context
- Group similar errors and alert you
- The AI developer Agent Sentry MCP connector can read Sentry issues inside chat and help investigate root causes
- AI developer Agent can then propose and implement fixes based on that investigation

So the workflow is: error appears in Sentry → AI developer Agent connector surfaces it → you or a developer asks AI developer Agent to investigate → AI developer Agent proposes a fix → you approve and it lands in the codebase.