Bug 56427 - m2mqtt on Mono
Summary: m2mqtt on Mono
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-05-14 14:52 UTC by St. VDH
Modified: 2017-08-21 20:33 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description St. VDH 2017-05-14 14:52:38 UTC
Severity	Code	Description	Project	File	Line	Suppression State
Error		Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: System.IO.FileNotFoundException: Could not load assembly 'M2Mqtt, Version=, Culture=neutral, PublicKeyToken='. Perhaps it doesn't exist in the Mono for Android profile?
Comment 2 Brendan Zagaeski (Xamarin Team, assistant) 2017-05-14 19:22:08 UTC
Non-engineering team preliminary quick review
(See https://developer.xamarin.com/guides/cross-platform/troubleshooting/questions/howto-file-bug/ for general reference.)




## Suspected to be a regression or a problem with a new feature?

Unknown.  The report does not mention the version of Xamarin.Android where the issue was encountered or whether the problem appeared after an update.




## Specific to one particular project, development computer, or target mobile device?

Probably.  When it appears as an Error (as in Comment 0), the message Comment 0 usually means that the library in question ("M2Mqtt" in this case) itself had an error during compilation.  This error should appear _in addition_ to the error mentioned in Comment 0 if the Error List is set to show Build errors from all projects.

The exact wording of the error message in Comment 0 appears also appears to be the older version of the wording, so the reporter in Comment 0 might be using an older version of Xamarin.Android.  (See also Bug 40782)




## Includes information about the environment where the bug was encountered, including the operating system and versions of Xamarin and any dependencies?

Not yet.  The report does not mention the version of Windows being used,the IDE, or the versions of Xamarin or any dependencies.




## Considers the relevant log files for the part(s) of the process where something goes wrong (IDE editing, MSBuild building, deploying, launching, attaching the debugger, an in-app error, or something else) and has them attached?

Not yet.  The error from Comment 0 is an error during MSBuild building.  The report does not yet include the diagnostic MSBuild output.
Comment 3 Brendan Zagaeski (Xamarin Team, assistant) 2017-05-14 19:23:19 UTC
## Next steps for the reporter (St. VDH)



1. Double-check the Error List to see if the M2Mqtt had any errors when building.  If the library didn't build, then the .dll for it won't exist, and that can cause the "FileNotFoundException" when trying to build the Android project that references it.



2. Collect, examine, and then attach back the diagnostic MSBuild output:

a. Set "Tools > Options > Projects and Solutions > Build and Run > MSBuild project build output verbosity" to Diagnostic.

b. The next time you build the project, the diagnostic MSBuild output will now be visible in the Output window.

c. Once you hit the error again, you can save the diagnostic MSBuild output to a file via "File > Save Output As..." and zip it up.

d. Attach back the zipped output file.



3. If steps 1 + 2 do not lead directly to the resolution, also collect and attach back the information about the environment where the bug was encountered, including the operating system and versions of Xamarin and any dependencies.



4. If it would also be possible to attach back a chopped down version of your full project that still demonstrates the problem, that would be perfect.



Thanks!
Comment 4 Jon Douglas [MSFT] 2017-08-21 20:33:36 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!