bug-hunter is assuming there's an assertion in interactive mode

[ddoherty03]

I am trying to debug a literate-style init file. I have followed the README instructions, given the name of the tangled init file, selected interactive mode with 'i', after testing in the new emacs instance and answering that the problem is not present with 'n', I get the following message:

Test failed.
The assertion returned nil after loading the entire file.
Remember, the assertion must be an expression that returns
non-nil in your current (problematic) Emacs state, AND that
returns nil on a clean Emacs instance.
If you're unsure how to write an assertion, you can try the interactive
hunt instead, or see some examples in the Readme:
    https://github.com/Malabarba/elisp-bug-hunter
interactive

That is, it looks like it assumed I am using an assertion instead of interactive.
I am using emacs version 28.0.50.

[NightMachinery]

I also have this issue, and I do not use a literate config file:

You have asked to do an interactive hunt, here's how it goes.
1) I will start a new Emacs instance, which opens a new frame.
2) You will try to reproduce your problem on the new frame.
3) When you’re done, close that frame.
4) I will ask you if you managed to reproduce the problem.
5) We will repeat steps up to 6 times, so hang tight!
Doing some initial tests...
Initial tests done. Hunting for the cause...
"/Users/evar/.emacs", line 155 pos 0:
  The assertion returned the following value here:
    t
  Caused by the following expression:
    (chemacs-check-command-line-args command-line-args)

GNU Emacs 27.1 (build 1, x86_64-apple-darwin20.3.0, NS appkit-2022.30 Version 11.2.1 (Build 20D75)) of 2021-03-13

[Ypot]

I have used one time the assertion mode, and now interactive mode is unusable.