ametad

Curious: what you get on command line interface when trying: ``` $ php artisan tenancy:run --tenant=1 route:list ``` I am having also problems with generating urls. Indeed, with 'URL::forceRootUrl()` the...

Sorry, maybe I hijacked your issue a little with my question... That wasn't my intention. I will open a new issue myself.

Hi @DennisOng and @luceos , Thankfully I am not the only one with this kind of problem. For some reason the events fired by this package are not being captured...

I am sorry I was not correct in my last post: the Hyn\\*\Events are fired and can be listened for in `\App\Providers\EventServiceProvider`. It is only confusing in what order, when...

Further more, var_dumping from `\Illuminate\Events\Dispatcher` in the fire() method, the `Hyn\Tenancy` events are showing up correctly! So this must have something to do with the order in which all things...

Do you also experience the behavior where the events are not 'heared' in `App\Providers\EventServiceProvider`?

Yes of course, here it is: ``` LIMIT_UUID_LENGTH_32=true TENANCY_DEFAULT_CONNECTION=tenant TENANCY_EARLY_IDENTIFICATION=true ``` Most of config/tenancy.php is the same, the things that are different in my file: ``` 'website' => [ 'disk'...

~~~I was thinking, because the events does only **not** show up (at least in the `EventServiceProvider`) in the early identified hostnames, perhaps the problem is te be found somewhere here(?):~~~...

@DennisOng Hope this helps you: I was so blindly staring at the **boot()** method, but I think registering listeners in the **register()** method of a Provider would do the trick....

It looks like there is a work around; don't auto discover `hyn/multi-tenant`. Like this: ```json composer.json "extra": { "laravel": { "dont-discover": [ "hyn/multi-tenant" ] } }, ``` config/app.php ```php 'providers'...