Migration is not applied with new auth module #4531

rezmeplxrf · 2026-01-03T09:28:53Z

rezmeplxrf
Jan 3, 2026

The sequence of commands I ran:

serverpod generate && serverpod create-migration --force
dart bin/main.dart --apply-migrations

Error after running dart bin/main.dart --apply-migrations
(Also, tried dart run bin/main.dart --apply-repair-migration and got the same result)

SERVERPOD version: 3.1.1, dart: 3.10.4 (stable) (Tue Dec 9 00:01:55 2025 -0800) on "macos_arm64", time: 2026-01-03 09:26:24.813080Z
runMode: development
serverId: default
role: monolith
loggingMode: normal
applyMigrations: true
applyRepairMigration: false
SERVERPOD initialized, time: 2026-01-03 09:26:24.851745Z
TIME                        ID         TYPE           CONTEXT                  DETAILS
--------------------------- ---------- -------------- ------------------------ ------------------------------
Unhandled exception:
DatabaseQueryException: { message: Table not found, have you applied the database migration? (relation "serverpod_auth_idp_email_account" does not exist), code: 42P01, position: 478 }
#0      _PgSessionBase._prepare (package:postgres/src/v3/connection.dart:199:35)
#1      _PgSessionBase.execute (package:postgres/src/v3/connection.dart:183:30)
#2      DatabaseConnection._query (package:serverpod/src/database/adapters/postgres/database_connection.dart:527:34)
#3      DatabaseConnection._mappedResultsQuery (package:serverpod/src/database/adapters/postgres/database_connection.dart:626:24)
#4      DatabaseConnection._deserializedMappedQuery (package:serverpod/src/database/adapters/postgres/database_connection.dart:659:24)
#5      DatabaseConnection.find (package:serverpod/src/database/adapters/postgres/database_connection.dart:77:12)
#6      Database.find (package:serverpod/src/database/database.dart:68:32)
#7      EmailAccountRepository.find (package:serverpod_auth_idp_server/src/generated/providers/email/models/email_account.dart:365:23)
#8      EmailIdpAccountUtils.listAccounts (package:serverpod_auth_idp_server/src/providers/email/business/utils/email_idp_account_utils.dart:70:28)
#9      EmailIdpAdmin.findAccount.<anonymous closure> (package:serverpod_auth_idp_server/src/providers/email/business/email_idp_admin.dart:199:45)
#10     DatabaseConnection.transaction.<anonymous closure> (package:serverpod/src/database/adapters/postgres/database_connection.dart:731:35)
#11     PgConnectionImplementation.runTx.<anonymous closure> (package:postgres/src/v3/connection.dart:591:32)
<asynchronous suspension>
#12     Pool.withResource (package:pool/pool.dart:127:14)
<asynchronous suspension>
#13     PoolImplementation.withConnection (package:postgres/src/pool/pool_impl.dart:153:16)
<asynchronous suspension>
#14     Database.transaction (package:serverpod/src/database/database.dart:399:12)
<asynchronous suspension>
#15     EmailIdpAdmin.findAccount (package:serverpod_auth_idp_server/src/providers/email/business/email_idp_admin.dart:196:13)
<asynchronous suspension>
#16     run (package:kindling_food_server/server.dart:77:19)
<asynchronous suspension>
#17     main (file:///Users/rezmeplx/Projects/school/kindling_food/kindling_food_server/bin/main.dart:6:3)
<asynchronous suspension>

My pubspec.yaml:

name: kindling_food_server
description: Starting point for a Serverpod server.

version: 1.0.0

homepage: https://www.example.com

environment:
sdk: '^3.8.0'

dependencies:
serverpod: 3.1.1
serverpod_auth_idp_server: 3.1.1

dev_dependencies:
lints: '>=3.0.0 <7.0.0'
serverpod_test: 3.1.1
test: ^1.25.5
very_good_analysis: ^10.0.0

serverpod:
scripts:
repair: serverpod generate && serverpod create-repair-migration
migration: serverpod generate && serverpod create-migration --force
start: dart bin/main.dart --apply-migrations
maintenance: dart bin/main.dart --apply-migrations --role maintenance
test: dart test
flutter_build: cd ../kindling_food_flutter && flutter build web --base-href /app/ --wasm && rm -rf ../kindling_food_server/web/app && mv build/web/ ../kindling_food_server/web/app

My migration_registry.txt

### AUTOMATICALLY GENERATED DO NOT MODIFY
###
### This file is generated by Serverpod when creating a migration, do not modify it
### manually. If a collision is detected in this file when doing a code merge, resolve
### the conflict by removing and recreating the conflicting migration.

20260103091103895

CREATE TABLE "serverpod_auth_idp_email_account" clearly exists in both definition.sql and migration.sql

CREATE TABLE "serverpod_auth_idp_email_account" (
    "id" uuid PRIMARY KEY DEFAULT gen_random_uuid_v7(),
    "authUserId" uuid NOT NULL,
    "createdAt" timestamp without time zone NOT NULL,
    "email" text NOT NULL,
    "passwordHash" text NOT NULL
);

rezmeplxrf · 2026-01-03T09:38:35Z

rezmeplxrf
Jan 3, 2026
Author

I've had to reset the postgres volume and manually apply the migration.sql using psql cli, to resolve this issue.

one thing I noticed is in server.dart I have code that uses final internalSession = await Serverpod.instance.createSession(); final emailIdp = AuthServices.instance.emailIdp;

I think this might be the problem?

0 replies

its-kios09 · 2026-01-13T16:06:39Z

its-kios09
Jan 13, 2026

Hi @rezmeplxrf

^IMO, I can see what's happening here. Your migrations are being created correctly, but there's a timing issue in your startup sequence that's preventing them from being applied, the error occurs because you're accessing the database during server initialization, before the --apply-migrations flag has a chance to execute. using dart bin/main.dart --apply-migrations. You need to ensure database operations happen after the server starts and migrations are applied.

Future<void> run(List<String> args) async {
  final pod = Serverpod(
    args,
    Protocol(),
    Endpoints(),
  );

  pod.addPostMigrationInitializer(() async {
    final session = await pod.createSession();
    try {
      final emailIdp = AuthServices.instance.emailIdp;
      // Your initialization logic here      
    } finally {
      await session.close();
    }
  });

  await pod.start();
}

Note: The fact that you had to manually run the migration via psql confirms the migrations themselves are valid - it's purely a timing issue in your initialization code.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Migration is not applied with new auth module #4531

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 2 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Migration is not applied with new auth module #4531

Uh oh!

Uh oh!

rezmeplxrf Jan 3, 2026

version: 1.0.0

homepage: https://www.example.com

Replies: 2 comments

Uh oh!

Uh oh!

rezmeplxrf Jan 3, 2026 Author

Uh oh!

its-kios09 Jan 13, 2026

rezmeplxrf
Jan 3, 2026

rezmeplxrf
Jan 3, 2026
Author

its-kios09
Jan 13, 2026