Seeders Not Working After NativePHP Build – How to Fix?

[KamilTahirli]

Hello, I am running NativePHP integrated with Laravel.

I have a CategorySeeder, which is called inside DatabaseSeeder. In my development environment, when I run php artisan native:db:seed, the seeder correctly sets the data into the SQLite database.

However, after running php artisan native:build on Linux, my seeders do not work.

Even if I add the following inside NativeServiceProvider:

Artisan::call('native:db:seed');
It still has no effect after the build.

Additionally, I added this to /config/nativephp.php:

'prebuild' => [
'php artisan native:migrate',
'php artisan native:db:seed'
],
But this also had no effect.

What do you recommend at this stage?

[PeteBishwhip]

This is correct behaviour. Seeders should ideally only be run in dev usually.

Although you used the prebuild key, the database is wiped out and made fresh for the build.

If you want the seeders to run in Production, you might want to add some logic to your service providers boot method to see if it's been seeded yet and if not, call Artisan::call('db:seed', ['--class' => 'CategorySeeder']);

[KamilTahirli]

This is correct behaviour. Seeders should ideally only be run in dev usually.

Although you used the prebuild key, the database is wiped out and made fresh for the build.

If you want the seeders to run in Production, you might want to add some logic to your service providers boot method to see if it's been seeded yet and if not, call Artisan::call('db:seed', ['--class' => 'CategorySeeder']);

Hello, as you can see from the topic, even though I manually run the seeders with Artisan in the NativeServiceProvider, there is no effect. :)

[PeteBishwhip]

You mentioned native:db:seed - Have you tried my suggestion of db:seed with the specific class specified and potentially the force attribute if required?

[KamilTahirli]

You mentioned native:db:seed - Have you tried my suggestion of db:seed with the specific class specified and potentially the force attribute if required?

I haven't tried it yet, but I think it shouldn't be necessary when it's local in the .env file. I had specified the --force attribute inside the prebuild array in nativephp, but there was no change.

[PeteBishwhip]

Prebuild will not work as I mentioned. We clear the database out before creating the package. The seeder needs to be run in your app after installation.

I'm not sure native:db:seed is what you need here. Let me know how trying my suggestion works for you.

[Kyazs]

@KamilTahirli we have similar problem. did you have solution for this?

in my NativeAppService provider i added this code.

        // Ensure the database is seeded if it hasn't been properly initialized
        if (Config::where('seeded', true)->count() !== 1) {
            Artisan::call('db:seed');
        }

but still, when i build its still give me an invalid credentials causing unable to login.
same thing on development. when i 'native:migrate:fresh' then run the 'native:dev' the code above doesnt work, it doesnt seed my database.