No Builds Available on TestFlight

You may find this issue when adding a new tester on the TestFlight page, question is how this user going to get the invitation.

Suppose you are adding a tester for version 2.4 and the error message looks like this.

All you have to do is go to the previous version 2.3 and add the new tester on that version. After the user accepts the invitation you won’t see the error for that user for any new versions.

Laravel Sanctum Tutorial Step by Step

Laravel Sanctum Tutorial Step by Step

Laravel Sanctum provides a featherweight authentication system for single page applications, mobile applications, and simple, token based APIs. Sanctum allows each user of your application to generate multiple API tokens for their account. These tokens may be granted abilities / scopes which specify which actions the tokens are allowed to perform.


composer require laravel/sanctum and composer update

Next, you should publish the Sanctum configuration and migration files using the vendor:publish Artisan command. 

php artisan vendor:publish --provider="Laravel\Sanctum\SanctumServiceProvider"
php artisan migrate 

You can also use following sql for creating table, if there is a problem to run migrate command.

CREATE TABLE `personal_access_tokens` (
   `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
   `tokenable_type` varchar(255) NOT NULL,
   `tokenable_id` bigint(20) unsigned NOT NULL,
   `name` varchar(255) NOT NULL,
   `token` varchar(64) NOT NULL,
   `abilities` text DEFAULT NULL,
   `last_used_at` timestamp NULL DEFAULT NULL,
   `created_at` timestamp NULL DEFAULT NULL,
   `updated_at` timestamp NULL DEFAULT NULL,
   PRIMARY KEY (`id`),
   UNIQUE KEY `personal_access_tokens_token_unique` (`token`),
   KEY `personal_access_tokens_tokenable_type_tokenable_id_index` (`tokenable_type`,`tokenable_id`)

Next, if you plan to utilize Sanctum to authenticate an SPA, you should add Sanctum’s middleware to your api middleware group within your application’s app/Http/Kernel.php file:

'api' => [
Laravel Sanctum Tutorial Step by Step

Download source code

Bitnami WordPress redirect www to non-www

I’m a big fan of Amazon Lightsail, I find it better than others for WordPress sites. Recently I was trying to redirect one of my WordPress websites, www traffic to non-www by updating .htaccess file but nothing was working.

After reading the Bitnami doc I found in Bitnami WordPress it handles differently.

Edit httpd-prefix.conf by vim or nano

vim /opt/bitnami/apps/wordpress/conf/httpd-prefix.conf
RewriteCond "%{HTTP_HOST}" ^$
RewriteRule "^/?(.*)" "%{REQUEST_SCHEME}://$1" [L,R=302,NE]

restart apache:

sudo /opt/bitnami/ restart apache

Everything should work.

Watch the video