LongPressGesture does not work as expected in Xcode Version 16.0 (16A242) and iOS 18

Question

Created Sep ’24

Replies 9

Boosts 8

Participants 7

When I copy and paste example code in apple developer documentation, LongPressGesture does not work as expected in Xcode Version 16.0 (16A242) and iOS 18. It seems updating(_:body:) method does not work when used with LongPressGesture. When I make a breakpoint in updating(_:body:) method and long press the blue circle on the screen of simulator(or device), it is expected to be caught in breakpoint or it is expected that color of circle turns from blue to red to green. However, it is not caught in breakpoint and never turns to red.

Question of Stackoverflow is about same issue and I can not use onLongPressGesture method to implement required feature of my app.

Development environment: Xcode Version 16.0 (16A242), macOS 14.5

Run-time configuration: iOS 18.0

Answered by Engineer in 803606022

Hello @minziikim, please use Feedback Assistant to submit a bug report, and please post here your bug report's ID.

Boost

Answer 1

Engineer OP

Apple

Sep ’24

Recommended

Hello @minziikim, please use Feedback Assistant to submit a bug report, and please post here your bug report's ID.

0

Answer 2

obrienser OP

Sep ’24

Same problem.

Version 16.0 (16A242d) macOS 15.0 iOS 18.0

0

Answer 3

austblake OP

Sep ’24

I'm having the same issue. Is this confirmed not to be working? Unfortunately use this in a ton of different spots throughout my app, so this bug makes it un-shippable.

0

Answer 4

minziikim OP

Sep ’24

@Engineer Please check FB15127375 . Thank you

0

Answer 5

austblake OP

Sep ’24

Have there been any updates here?

0

Answer 6

Mikhail228 OP

Sep ’24

+1 Have the same problem and it's just breaking my app, because the primary action is a long press gesture

0

Answer 7

smorlan OP

3w

Same problem here... unfortunately the app is already deployed on the store and the navigation is not working well... When you press twice, long press gesture starts to work though.

0

Answer 8

austblake OP

3w

Ive also posted this feedback as FB15275234

0

Answer 9

pedruu OP

5d

This seems to not work still on 18.1, is there an update about this?

0