blocks|key|928996|text|在第一个"didSelectRow“之后禁用用户交互。在转换过程中，可能会有多个点击“堆叠”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|928997|通常需要手指灵巧的人才能做到这一点，但仍然如此。|928998|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Disable user interaction after the first "didSelectRow". It's possible for multiple taps to "stack up" during the transition.

It usually takes someone with amazing dexterity in their fingers to get this behavior, but still.

blocks|key|929057|text|我也看到了这个问题，可能每1000个用户中就有一个受到影响，或者更少。我с可以清楚地看到两个相继注册50毫秒的didSelectRowAtIndexPath。我猜测这是iOS中的一个错误--一旦推送了新的视图控制器，就不应该有新的点击指向旧的视图。遗憾的是，很可能要由我们来编写代码来防范这种情况。我是这么想的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|929058|++++-+(void)tableView:(UITableView+*)tableView+didSelectRowAtIndexPath:(NSIndexPath*)indexPath+{
++++++++if+(self.navigationController.topViewController+!=+self)++++++++
++++++++++++return;

++++...+do+other+stuff

++++}|code-block|syntax|javascript|929059|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I'm seeing this problem too, probably one out of a 1000 users gets affected, or less. I сan clearly see two didSelectRowAtIndexPath registering 50 ms one after another. My guess is that it is a bug in iOS - no new taps should be directed to old view once new view-controller has been pushed. Alas, it is likely up to us to write code guarding against this. Here's what I'm thinking:

<pre><code> - (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath*)indexPath {
 if (self.navigationController.topViewController != self) 
 return;

 ... do other stuff

 }
</code></pre>

blocks|key|713045|text|这是因为您在didSelectRowAtIndexPath方法中使用了段。确保这个段是通过ctrl从源视图控制器顶部的视图按钮拖动到目标视图控制器来创建的。通过按ctrl键从表格视图单元格拖动到目标视图控制器来创建分段时，会出现错误。您不需要更改任何代码。只需删除段并以正确的方式创建它。如果我没弄错的话，希望这能解决你的问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|713046|entityMap^0|6|N|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

This occurs because of the segue you are using inside the <code>didSelectRowAtIndexPath</code> method. Ensure that this segue is created by ctrl dragging from the view button on top of the source view controller to destination view controller. The error occurs when you create the segue by ctrl dragging from the table view cell to destination view controller. 
You do not need to change any of you code. Just delete the segue and create it in the correct way. Hope this solves your problem, if I got the question right.

blocks|key|713093|text|如果你已经创建了Storyboard+Segue，不要调用；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|713094|[self+performSegueWithIdentifier:@"TYPE"+sender:self];|offset|length|style|CODE|713095|在这种方法中；|713096|-+(void)tableView:(UITableView+*)tableView+didSelectRowAtIndexPath:(NSIndexPath+*)indexPath|713097|entityMap^0|0|0|1I|0|0|0|2J|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

if you already created Storyboard Segue don't call;

<code>[self performSegueWithIdentifier:@"TYPE" sender:self];</code>

in this method;

<code>- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath</code>

Under certain circumstances, UITableView <code>didSelectRowAtIndexPath</code> is being called twice causing the error <code>Pushing the same view controller instance more than once is not supported</code>. 

Here's are the sequence of events:

<pre><code>TableView::didSelectRowAtIndexPath. 
TableView::viewWillDisappear. 
PushedViewController::viewWillAppear. 
TableView::didSelectRowAtIndexPath. 
Error: Pushing the same view controller instance more than once is not supported' 
</code></pre>

The only thing worth noting is that the UITableView is loading images asynchronously, but that never calls <code>didSelectRowAtIndexPath</code>. Also, the PushedViewController is reused to avoid having to reload it each time a cell is selected in the UITableView.

Anyone have any idea what may be causing this? 
Thanks.

UITableView didSelectRowAtIndexPath called twice

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

在某些情况下，UITableView didSelectRowAtIndexPath会被调用两次，从而导致错误Pushing the same view controller instance more than once is not supported。以下是事件的顺序：TableView::didSelectRo...

问UITableView didSelectRowAtIndexPath调用了两次
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问UITableView didSelectRowAtIndexPath调用了两次EN