mantine: Status wont change for accept/unaccepted types on Dropzone

What package has an issue

@mantine/dropzone

Describe the bug

When i select/drop files onto drop zone, the “status” doesnt change at all. Either i upload an image or a document, it wont judge the mime type , causing accepted and rejected to be always false.

I am using mantine 3.4.0 with dropzone also on 3.4.0

 <Dropzone
                  className="mt-10"
                  onDrop={(file) => {
                    console.log(file);
                  }}
                  maxSize={3 * 1024 ** 2}
                  accept={[
                    "image/png",
                    "image/jpeg",
                    "image/jpg",
                    "image/sgv+xml",
                    "image/gif",
                  ]}
                  loading={loadingUpload}
                >
                  {(status) => (
                    <Group
                      position="center"
                      spacing="xl"
                      style={{ minHeight: 220, pointerEvents: "none" }}
                    >
                      <ImageUploadIcon
                        status={status}
                        style={{
                          width: 80,
                          height: 80,
                        }}
                      />

                      <div>
                        <Text size="sm" inline>
                          Drag images here or click to select files
                        </Text>
                        <Text size="sm" color="dimmed" inline mt={7}>
                          Attach as many files as you like, each file should not
                          exceed 5mb
                        </Text>
                      </div>
                    </Group>
                  )}
                </Dropzone>

In which browser did the problem occur

All

If possible, please include a link to a codesandbox with the reproduced problem

No response

Do you know how to fix the issue

No

Are you willing to participate in fixing this issue and create a pull request with the fix

No response

Possible fix

I have no idea what went wrong.