I can confirm this one 👍 Having same problems after the change.

Temporary workaround: use MockBuilder#replace

@Component({
  selector: 'app-nested',
  standalone: true,
  template: ``,
})
class NestedComponentStub {
  public readonly anchor = signal(new ElementRef(undefined)).asReadonly();
  public readonly name = input.required<string>();
}

describe('my sandbox', () => {
  beforeEach(() =>
    MockBuilder(TargetComponent).replace(NestedComponent, NestedComponentStub)
  );

@satanTime this seems to be a better fix: simply remove the view queries, as they’ll always be null anyway

  const generateFinalQueries = (queries: { 
    [key: string]: Query; 
  }): [Array<[string, Query & { ngMetadataName?: string }]>, string[]] => { 
    const final: Array<[string, Query & { ngMetadataName?: string }]> = []; 
    const scanKeys: string[] = []; 
   
    for (const key of Object.keys(queries)) { 
      const query: Query & { ngMetadataName?: string } = queries[key]; 
-     final.push([key, query]); 
   
      if (!query.isViewQuery && !isInternalKey(key)) { 
+       final.push([key, query]);
        scanKeys.push(key); 
        final.push([`__ngMocksVcr_${key}`, cloneVcrQuery(query)]); 
      } 
    } 
   
    return [final, scanKeys]; 
  }; 

This will be fixed by the same fix as #7976, is my guess.

Good evening, any news?

Hello, any updates on this issue?

I guess #8895 is a similar problem.

Any news on this issue? This bug really prevents using the new API.

The fix here is not to mock the component but pass it into your test declarations with you parent component

Sorry for the delay. I'll take a look closer next week.

@satanTime, did you already have a chance to look into it?

Another workaround I found until this is fixed:

MockInstance(YourComponent, 'viewChildElement', signal(new ElementRef(document.createElement('div'))));

@satanTime, sorry to bother you again, but do you have any updates on this? I guess you have currently limited time to work on a request like this, right? No hard feelings, the effort of this great library is definitely appreciated. :)

Confirmed. If you try to mock a component that uses a viewChild signal inside, it will give error.

cc @satanTime

I can confirm, happening for me as well.

Hey @Francesco-Borzi fancy seeing you here :D

+1 on this issue. Happening on 14.13.1 here.

So @satanTime is this on the list to fix soon as well?

We are also having this issue.

I'm having also the same problem

Another workaround I found until this is fixed:

MockInstance(YourComponent, 'viewChildElement', signal(new ElementRef(document.createElement('div'))));

Ok so this workaround works but I had some difficulties to apply it. So here is a more verbose explanation that is working in my case:

describe('my tests', () => {
  // Define a scope to auto-clean mocked instance see https://ng-mocks.sudo.eu/api/MockInstance/#scope
  MockInstance.scope();

  beforeEach(async () => {
       // Put expected TestBed conf WITH the broken MockComponent(MyComponent)
       await TestBed.configureTestingModule [...]
       
       // Override the viewChild element with a viewChild-matching-type mock
       // (can be ElementRef as in the previous answer or Component, etc depending on your code)
       MockInstance(MyComponent, 'myViewChild', signal({} as MyViewChildComponent));
  });

  it('my test', () => {
      // test
  });
});