viktor hesselbom

```javascript /** @jsx h */ import { h, render } from 'preact' import { Router, Link } from 'preact-router' import createHistory from 'history/createBrowserHistory' let history = createHistory() history.block('Are you sure...

Neither did I until I conveniently found it when needed for a very specific use case! ;)

May I ask if there's any progress in merging this PR? I'm currently using the fallback suggested [here](https://github.com/nextauthjs/next-auth/issues/6788#issuecomment-1658765772) but with that the email is reported as null since it can't...

Personally, I don't mind this page if it's technically required, but would love some way to style it, like injecting some CSS to make it look more like the app.

An interesting finding. It looks like the issue happened between version 1.4.5 and 1.4.6 because if I change the Swift package to use version 1.4.5 and run the following code...

Next finding! If I change the code to the following (`parsingType: .generic`, with the latest version, 1.4.8) it sort of works: ```swift if let fit = FitFile(file: selectedFile, parsingType: .generic)...

Go ahead, it's a simple test file for me too.

Awesome! I noticed one thing though, I now get the value with offset already applied. So in this case I get "custom_target_heart_rate_low" as 140 but it should be 240 so...

Sounds like it should work. For HR any value above 100 is considered absolute (offset by 100) and below relative. So a value of 70 would be 70% of max...

I see, terrific! My test file was generated from a service that only deals with absolute values. Could try looking around for one dealing with relative ones.