I think I saw this with previous app and firmware version too, but it seems worse with app v1.15 and firmware 2.30.
Here's how it plays out. I fire up the Seestar, pick my first target and GoTo. It goes through all the usual alignment, locating etc, lands on my target, and I start capture. It usually works this first time (when it doesn't.. same symptoms as below).
But maybe I find that the first target it not that interesting, or too dark (wish the sky atlas included information about brightness of the object). Anyway, while the first one is capturing, I dig around in the Atlas for something new, and when I find it, I hit Go To, and it ends the current capture and heads off to the new location.
Once found, I can sit there on the preview for a minute and see that it's tracking it perfectly. No drift at all.
But then I start the capture,.. 10 seconds pass.. 20.. 30.. finally it tells me the first image is unusable due to trails or not enough stars (even though there are plenty in the preview). Sometimes it still shows this first image with trails (onto which there's no way it can stack further). Sometimes it just doesn't capture anything. I'll let it go 6 more exposures (and it tells me the first 3 have failed) so I stop it, and sure enough in the preview I see the stars slowly moving across the preview now as though it has stopped tracking completely.
So I skew back to where I started.. stop.. verify that it's tracking properly again (nothing moving on screen), start capture, and it does it again (loses tracking, sometimes shows image with trails and won't stack anything).
Or, I go back to atlas and tell it to re-go to the same object.. it does so.. I verify it's tracking.. start capture.. same issue.. rinse repeat.
It's very frustrating. There can be no legit reason why the preview should show it tracking perfectly, and then it gives up when it starts capture.
I've had a little success sometimes when I see it drifting immediately after it fails, just bumping the manual skew once in the direction it's drifting, it stops holds.. and I then I start capturing. Might just be a fluke though. Once it starts stacking properly then it rarely has an issue again after that. It's just getting it started that is the problem.
Twice I've fired up screen recording to demonstrate the issue, and of course it immediately starts working properly, although I think I got the "not enough stars" once, while there were plenty of stars visible.
Anyone else seeing this behavior?