Note that there are some explanatory texts on larger screens.

plurals
  1. POGet EntCannotSeeExistenceException trying to post to "/me/feed" with a test user
    text
    copied!<p>Developing a WP7 app, and I'm trying to post something to the user's feed. We have all this working on iPhone already, and we have a test account created already. With the iPhone it's able to post to our test user's page.</p> <p>I'm trying to use the Facebook C# sdk to do the same thing, using the same account. I can successfully login to the test user's account and obtain the AccessToken. When I login, the extended permissions I request from the user are "read_stream", "publish_stream", "publish_checkins".</p> <p>When I try to do something like this:</p> <pre><code>var client = new FacebookClient(access_token); var parameters = new Dictionary&lt;string, object&gt; { { "message", "Howdy!" } }; client.PostAsync("/me/feed", parameters); </code></pre> <p>Then it fails, and observing client.PostCompleted I see the error is:</p> <blockquote> <p>(EntCannotSeeExistenceException) The entity (class EntPlatformTestUser) backed by id 1234 cannot be seen by the current viewer 1234 (EntID: 1234)</p> </blockquote> <p>I found a blog post[1] where someone was running into this exception, and he solved it by switching out of sandbox mode. But we're already not in sandbox mode. Plus, as I described above, everything is working just fine using the iPhone SDK. This leads me to think that I'm just doing something wrong with the C# SDK.</p> <p>[1]. <a href="http://test.ical.ly/2011/03/10/facebook-graphapi-uncaught-entcannotseeexistenceexception-the-entity-class-entapplication-backed-by-id-12345-cannot-be-seen-by-the-current-viewer-12345-entid-12345/" rel="nofollow">http://test.ical.ly/2011/03/10/facebook-graphapi-uncaught-entcannotseeexistenceexception-the-entity-class-entapplication-backed-by-id-12345-cannot-be-seen-by-the-current-viewer-12345-entid-12345/</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload