Do you fix all bugs before rolling out your MVP?

If the bugs are affecting your app's core functionality, please fix them before release.
If not affecting your primary user functions, launch it asap.

I just make it clear that it is an MVP or beta or under construction.

If you are not slightly disappointed with your initial product you are not launching early enough.

No.

If the MVP truly solves an important problem, users will endure the bugs. Plus, it's much more valuable to get first hand feedback from customers as soon as possible rather than delivering a "perfect" product.

You can't be able to fix all the bugs. Prioritize the bugs that affect the core functionality of the product. The rest of the bugs can be fixed ongoing basis.

You can try to, but bugs will always pop up. No product, whether it's a MVP or live product is 100% complete.

If your core flow is breaking then, yes.

it depends what what bugs are and what is your app about. if you are releasing a product that will be used for mission critical ops (medical, security etc) you might want to be more careful :)

there will always be bugs. Just make sure that your MVP is actually Viable. So if it delivers on the main value it promises, then go for it. and keep fixing.

You can think that you've fixed all the bugs, but eventually, you'll surely get feedback from your customers regarding new bugs, or about some that you've missed during testing :)

No, but just make sure you're clear about the fact there is some bugs left

As much as possible, but my philosophy is - if an app has to be 100% "perfect" than the market is way too saturated/competitive for me.

I would suggest not to ship any bugs that could degrade user experience. Fix them if they don't take too long to fix. If it would take too long to fix, then disable the feature so users don't get confused. You could give a popup saying something such as "This feature will be ready soon!"

Fix the essential things that might impact your business. There's no perfect product regardless of the release cycle by any company. You'd be surprised all the waivers we needed for the technology to move forward

An MVP can tolerate some minor bugs as long as you let everyone know it's an MVP
Reid Hoffman said something meaning full on the topic: "starting a company is like jumping off a cliff and assembling a plane on the way down"

you take a little more time and set all your bugs that you know because when your app is live then there are other options and review you work that's why you need to fix all the know bugs and then live the app so that after you focus on the marketing and other improved features not on the previous ones.

I think it's counter productive to fix all the bugs you can think of before rolling out your MVP.
It all depends on the bug and how likely a user will encounter it and affect its perception/trust of your product.

In summary I'd say to trust your gut and do what you think is best for your users to have a good impression of your product and forgive you the small issues they encounter.

I fix any bug which are show stoppers. Rest of the minor bugs , I will fix them once I see some kinds of traction.