我正在使用 TWTweetComposeViewController(如果可用)从我的 iOS 应用程序内部发送推文.我使用样板文本预先填充视图控制器，然后让用户自行修改和发送.它在大多数情况下都很好用.蒸馏下来，它看起来像这样(body 指向一个有效的 NSString):
I am using TWTweetComposeViewController, when available, to send tweets from inside my iOS app. I pre-populate the view controller with boilerplate text, then let the user modify and send at their discretion. It works great for the most part. Distilled down, it looks like this (with body pointing at a valid NSString):
if (NSClassFromString(@"TWTweetComposeViewController")) {
TWTweetComposeViewController *iOS5twitter = [[TWTweetComposeViewController alloc] init];
[iOS5twitter setInitialText:body];
iOS5twitter.completionHandler = ^(TWTweetComposeViewControllerResult result)
{
[self.viewController dismissViewControllerAnimated:YES completion:nil];
};
[self.viewController presentViewController:iOS5twitter animated:YES completion:nil];
[iOS5twitter release];
}
else {
/* Do something else when the framework is missing */
}
现在如果 body 太长，即超过 140 个字符，则生成的推文视图根本没有任何文本，字符倒计时设置为 140.在这种情况下，我可能预计会截断，虽然它似乎没有在类参考中以一种或另一种方式记录在初始文本太长时会发生什么，但我可以接受在传递给 setInitialText 之前我必须截断到最大推文长度.
Now if body is too long, i.e., more than 140 characters, the resulting tweet view is empty of any text at all, character countdown set to 140. I might have expected truncation in this case, although it does not appear to be documented in the Class Reference one way or the other what happens when the initial text is too long, but I can accept that I have to do the truncation to maximum tweet length before passing to setInitialText.
我不明白的是，某些短于 140 个字符的消息也会产生空的推文视图.
What I don't understand is that certain messages which are shorter than 140 characters also produce the empty tweet view.
最初，我看到一个似乎完全有效的字符串，但失败了 139 个字符.我注意到缩短字符串使它起作用.但经过大量试验后，我还注意到，用相同长度的随机文本替换恰好出现在文本中的 URL 可以正常工作.换句话说，是 URL 本身造成了问题.
Initially I saw what seemed to be a perfectly valid string with 139 characters failing. I noticed that shortening the string made it work. But after a great deal of experimenting, I also noticed that replacing a URL which happened to appear inside the text with random text of the same length made it work. In other words, the URL itself is causing a problem.
所以我认为我使用的 URL 可能有些奇怪，但我将其提炼成这一点.这个有效:
So I thought maybe there was something weird about the URL I was using, but I distilled it down to this. This one works:
NSString *body = @"............................................................................................................................................";
虽然没有
NSString *body = @"............http://a........................................................................................................................";
观察:
[body length] 以这种方式报告).唯一的区别是在第二个的中间嵌入了一些类似 URL 的东西.[body length]). The only difference is the presence of something vaguely URL-like embedded in the middle of the second one.有人见过这样的吗?知道发生了什么吗?是我做错了什么，还是 iOS Twitter 框架刚刚损坏?
Anybody ever seen something like this? Any idea what is going on? Am I doing something wrong, or is the iOS Twitter Framework just broken?
我遇到了完全相同的问题.这是 Twitter 框架中的一个已知错误，正在跟踪中.
I have run into the exact same problem. It is a known bug in the Twitter framework and is being tracked.
请在 dev.twitter.com 上查看此讨论 https://dev.twitter.com/discussions/5024
Please see this discussion on dev.twitter.com https://dev.twitter.com/discussions/5024
(如果可以的话，我会把它作为评论而不是答案发布，但我没有足够的可信度，所以我想我也会添加以下观察结果，以防它们感兴趣).
(I would have posted that as a comment rather than an answer if I could, but I don't have sufficient SO credibility so thought I'd add the below observations as well in case they are of interest).
仅添加不带 URL 的文本时，字符数按预期工作.使用 addURL: 方法添加 URL 会导致使用 21 个字符的推文(20 个用于 URL 加上一个空格).在初始文本中添加 URL 会导致 URL 使用 20 个字符.当包含单个 URL(使用任一方法)时，当总字符数超过 138(例如，URL 为 20 + 空格 + 初始文本的 117 个字符)时，框架会失败，因此会丢失 2 个字符.只有一个 URL，设置初始文本然后使用 addURL: 添加 URL 的顺序没有区别.
When just adding text without URLs, the character count works as expected. Adding a URL with the addURL: method causes 21 characters of the tweet to be used (20 for URL plus a space). Adding the URL in the initial text causes 20 chars to be used for the URL. When including a single URL (using either method) the framework fails when the total character count exceeds 138 (e.g. 20 for URL + space + 117 chars of initial text) thus losing 2 characters. With just one URL the order of setting the initial text and then adding the URL with addURL: does not make a difference.
当添加 2 个 URls 时，当总字符数超过 113 时它会失败，这会丢失 27 个字符！但是，如果有 2 个或更多，如果您在 BEFORE 设置初始文本时添加 URL，则会失败，总数为 136.因此每个 URL 再次丢失 2 个字符.
When adding 2 URls, it fails when the total character count exceeds 113 this losing 27 characters! However, with 2 or more, if you add the URLs BEFORE setting the initial text, it fails with a total count of 136. So 2 chars are lost per URL again.
总结/解决方法 - 如果只包含 1 个 URL，那么在初始文本中添加它会比使用 addURL: 方法多出一个字符，但总体上仍然会少 2 个字符.如果使用 addURL: 添加 2 个或更多 URL，则在初始文本之前添加它们，但在修复错误之前，每个 URL 仍然会丢失 2 个字符.
Summary/Workaround - if just including 1 URL then adding it in the initial text will give you one extra character than using the addURL: method, but you will still be short 2 characters overall. If adding 2 or more URLs using addURL: then add them before the initial text, but until the bug is fixed, you will still lose 2 chars per URL.
我已经提交了雷达，但是根据这个 我可以浏览其他人 (Apple) 的错误报告?，错误报告的次数越多，它的优先级就越高，因此值得其他人也提交它以提高它的优先级.
I have filed a radar, but according to this Can I browse other people's (Apple) bug reports?, the more times a bug is reported the higher priority it is given, so it is worth others filing it as well to increase it's priority.
这篇关于TWTweetComposeViewController 中的错误?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！