I have the same problem. It was because my tabset add tabs with an *ngFor directive and it waits a callback. I fix it with a 900ms setTimeout()

ngAfterViewInit(): void { setTimeout(() => { this.userTabSet.setActiveTab(1); }, 900); }

Dear @4ntibala 

Could you please explain one more time, what do you want to achieve?

I think that I didn't understand you good.

Best Regards,

Damian

Dear @4ntibala 

I don't think, that this problem is related to the latest MDB Angular update, but feel free to download some older version, and test.

I have added this problem to our bugs list, and we'll fix it.

Best Regards,

Damian

this.caseTabs.click(Event.AT_TARGET, 1);

but like this the

(getActiveTab)="onTabChange($event)

does not get triggered. what could i pass to the .click function in order to imitate a tab activation?

hey, my code is 

ngAfterViewInit() {
this.caseTabs.setActiveTab(1);

this.caseTabs.tabs[0].disabled = true;
this.caseTabs.tabs[2].disabled = true;
}

still, the active tab does not get set and it shows the deactivated tab [0]. might this error be related to the last mdb version update?

this.caseTabs.click(Event.AT_TARGET, 1);

will bring u closer..

Dear She Jong Shon,

The @ViewChild decorator is available to use after rendering the page, not in initializing part.

So please use it in the ngAfterViewInit() lifecycle instead of ngOnInit(), and everything will be working fine.

Best Regards,

Damian