Hi Sravanthi, I followed the steps you have outlined and I can confirm that the fridgeclient/ fridgeserver app behaves as expected. You must be seeing a bunch of ?Got a response from? messages followed by the blank spaces on the fridgeclient app. This essentially means that the client successfully received a notification from the server after finding a resource. The client is finding all the resources which the server is hosting, but the resource Uri is not getting printed. This issue is due to a bug in OCRepresentation.getUri() in C++ SDK. You can track the bug here: https://jira.iotivity.org/browse/IOT-769
You can also try fridgegroupclient/ fridgegroupserver examples. In these examples, the client creates resource proxies (child resources) of the resource hosted by the server and reads their values. This has more detailed logging information but has the same Uri not printed issue as discussed above. Let me know if you have additional questions. Thanks, Rahul From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Sravanthi Mulagondla Sent: Wednesday, October 28, 2015 3:11 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] Regarding Iotivity android examples HI, 1. Downloaded iotivity-1.0.0.zip and extracted. 2. Compiled iotivity-1.0.0 for android with arm architecture. 3. Imported sample android example projects into Androidstudio 4. Generated .apk files for all projects. 5. While running DeviceDiscoveryServer and DeviceDiscoveryClient with two arm phones with lollipop Os. 6.Server waiting for the requests and client is Querying for device information. 7.Now tried with FridgeClient and Fridgeserver 8.Server created Light,Door,Resorces ,Client Intiating fridge discovery but It is not finding any resources. Can you please help me for this problem as early as possible? I was struggling from one week. Thanks®ards, Sravanthi. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20151028/0bc66271/attachment.html>
